AEM as a Cloud Service is the latest member of the growing AEM family of products and it offers some significant advantages over the previous AEM products – AEM on premises and AEM Managed Services. It represents the biggest jump for AEM in a decade.
As other cloud services AEM as a Cloud can give your organizations serious performance boost, major improvement of the stability and accessibility of your AEM systems, it could take care of most of your AEM maintenance work and also simplify the development and distribution of custom software for your AEM instances. AEM as a Cloud is always on, always at scale, always current, and always evolving.
By comparing the new AEM as Cloud versus having AEM instances running on your own server we can see where many of the advantages of the new service offered by Adobe come from.
Architecture and Environments
If your organization uses AEM on premises then most likely you are maintaining several servers for the Author and Publish instances as well as their Web servers for AEM Dispatchers and on top of that possibly a Load Balancers like F5 as an entry point for your clients or content users. All that is probably maintained by your teams. New content is probably transferred from Author to Publish constantly or even vice versa. Updates need to be performed on premises and if you decide to upgrade to the next AEM version this might take weeks. All that would no longer be the case if you moved to the Cloud as Adobe will offer as many Author and Publish services you need and they will will be maintained and updated regularly.
AEM as a Cloud offers dynamic architecture with variable number of AEM instances with no downtime for maintenance tasks. How is Adobe able to achieve that when your organization could have thousands of pages and assets? When you create or upload content into AEM as a Cloud it will be stored separately from the actual Author or Publish services that your users or customers will use. All the processing of that content like creating asset renditions will also be executed separately on the Datastore where your content is held resulting in noticeable performance boost and also allowing for a quickly scalable architecture based on the actual traffic and activity.