Cloud computing presents the single largest opportunity for IT organizations today. There are a number of factors to take into consideration. The following considerations take a holistic approach to the Application Lifecycle Management (ALM) process.
Developing applications in the cloud vs. traditional corporate infrastructure requires a number of changes; the first of which is architecture. Cloud infrastructure is often both shared and unprotected and architectural changes for cloud can provide greater resilience and opportunity.
Testing in the cloud
Unlike applications built on traditional corporate infrastructure, testing with shared infrastructure that may be spread across different solutions presents a new set of challenges. If the application is setup for scaling, it only adds to the complexity. Plus, the testing needs to happen externally. These are only a few of the challenges for testing applications in the cloud.
Aside from the tactical aspects of the development process, there are strategic considerations that affect the lifecycle management process. When applications are within the data center, it is often easier to manage resources, track utilization and manage the application or service. With cloud, the dynamics change. Once the infrastructure is established, the methods to manage traditional functions become a bit, well, cloudy.
In addition to lifecycle management changes, the underlying visibility issue can present a challenge to effective resource management. Application developers need enablement, but frameworks are needed to avoid cloud sprawl. As with many things, it’s a matter of balance and thinking ahead.