Like an automobile, a web application needs occasional maintenance and management over its life cycle. Although it doesn't need oil changes, it will probably need version upgrades. There may not be manufacturer recalls, but sometimes servers fail or hang. An application doesn't need to be washed and detailed, but it does need to be backed up. And both cars and applications need occasional performance tuning.
In this new Standing Cloud white paper, Application Lifecycle Management, CEO Dave Jilk provides a comprehensive point-by-point check-list of the system maintenance and management functions that should be performed on a standard architecture web application, with a particular emphasis on doing so in an Infrastructure-as-a-Service (IaaS) environment. (Think of it as the Car Talk for the cloud.)
Sure, with Software-as-a-Service (SaaS) you may be able to avoid most, if not all, of this maintenance. But the trade-off is the loss of some flexibility and control. On-premises deployments require a staff person or contractor to manage it all.
But with the right tools and the infrastructure cloud, most of it can be automated. In Infrastructure-as-a-Service world, most of these procedures can be automated or automated with manual initiation; and further, they can be performed in ways that are more reliable and testable than in a bare-iron data center. In fact, with an appropriate IT Process Automation system, a single-tenant application deployment in the cloud can be almost as easy as Software-as-a-Service, but without the attendant loss of control and flexibility.