A paper for technical decision makers who want to learn how to deploy Magnolia in the cloud
Cloud computing happens on shared resources in the Internet. Services are provided to computers on demand, like water, electricity and other utilities. A benefit to administrators of digital business platforms is simplicity as they no longer need to know all the details of the underlying technology and infrastructure - the cloud provider takes care of that. The provider offers dynamically scalable, virtualized resources that can be managed with Web-based tools.
Magnolia is typically deployed as a stand-alone system on a local server. This means that each Magnolia instance runs on separate hardware or in a separate virtual machine. In order to scale up, you add more physical servers or deploy more virtual machines. In this setup, each Magnolia instance is completely independent. You can shut it down and start it up as you wish, independent of other instances.
Contrast this with a cloud setup. In a cloud, Magnolia is deployed to virtual infrastructure such as Amazon EC2 or Rackspace Cloud. A master deployment image (start state) is created in the cloud. You clone the master to deploy new Magnolia instances. Each clone is an exact copy of the master.