Explore what AEM as a Cloud Service and Edge Delivery Services are, and the value they deliver.
Hello and welcome everyone. My name is Abhishek Dwevedi, and in this video, we are going to learn about, AEM as a Cloud Service.
After completing this video, you should be able to define AEM as a Cloud Service, and you should also be able to explain benefits of AEM as a Cloud Service.
AEM as a Cloud Service, introduces the next generation of AEM production line.
AEM as a Cloud, is a cloud-native solution, and provides significant benefits in terms of scaling and performance, while preserving and extending all AEM use cases and functionalities.
The cloud-native nature of AEM as a Cloud Service allows business practitioners to have better user experience with faster performance and the latest innovations deliver to them regularly.
It also allows marketing professionals to experience quicker time to a value as AEM as a Cloud has got deeper integration with Adobe Experience Cloud Solutions.
One of the major evolutions of AEM as a Cloud Service is the generalized use of Adobe IDs for accessing the author tier, which also results into single sign on across all Adobe Cloud applications. For instance, if a user logs first into Cloud Manager, or on AEM Sites Cloud Service instance, or on AEM Assets Cloud Service instance, or even Adobe Analytics, then this user won’t have to log in in any of the other four solutions.
Also, user profile information is centralized in the Adobe IMS system.
Eventually, profile information and provide related information such as notification will be shared across all these Cloud Services. On the other hand, user preferences, remain local to each particular instance of the AEM as a Cloud Service.
With AEM as a Cloud Service, developers can fully concentrate on configuring and extending AEM following the same patterns that have made AEM successful over the years. While they can also argument, with new cloud-based development patterns.
With AEM as a Cloud Service, system administrators don’t have to worry about infrastructure and operations. Thanks to a fully automated service in AEM as a Cloud, where most infrastructure and operations tasks are automated.
One of the major changes coming with AEM as a Cloud Service is the ability for all services, author and publish to be always on, in the past, especially on the author site, there was a need to periodically stop the service for different types of maintenance operations like updates, patches, upgrades, and some routine maintenance operations. For some customers, this could have resulted in our soft scheduled downtime on weekly basis. With AEM as a Cloud Service, all these operations are now fully automated in a way that does not result in any interruption of service for the business practitioners.
Various elements of AEM as a Cloud Service architecture, are also self-healing. They are equipped with readiness and liveliness health checks. If for some reason a particular node of architecture is deemed unhealthy, then it is removed from the service and silently replaced with a new healthy one. The AEM Cloud operations are supported by a whole new monitoring, reporting and alerting infrastructure, allowing the Adobe’s Site Reliability Engineers to proactively keep their service healthy.
The other benefit of AEM as a Cloud Service is, it’s always at scale. All instances of AEM as a Cloud Service are created equal with the same default sizing characteristics, in terms of number of nodes, and how much memory and compute capacity are allocated to each of them.
AEM as a Cloud Service is based on the use of orchestration engine, that constantly monitors the state of the service, and dynamically scales each of the service instance as per the actual need, both scaling up and down. This is true for the number of nodes, the amount of memory and the allocated CPU capacity on each node.
It also allows to accommodate, varying traffic patterns for our customers.
The scaling of pertinent instance of the service can be both automatic or manual and it can be on two axes. The vertical axis, with the amount of memory and the CPU capacity can be scaled up or down for fixed number of nodes, or horizontal axis, where the number of nodes for a given service can be increased or decreased.
Out of all the changes coming with AEM as a Cloud Service, the ability to be always current is probably the most significant for our customers. Adobe proactively takes care of updating all running instances of the service to the latest version of AEM code base on frequently basis, up to daily updates. The updates are happening silently with no interruption on service.
Most updates are done for maintenance and security reasons. Customers are updated with the latest bug fixes and the customer experience is not significantly impactor. Most upgrades are small and incremental, which also differs a lot from how we used to release AEM Quickstart major releases and service packs which used to contain thousands of different changes in one major release.
The other benefit of AEM is a Cloud Service is, it’s always learning, is always up to date with the performance enhancements and security updates.
AEM as a Cloud Service evolves on daily basis, based on the projects implemented by our customers. Content, code and configurations are constantly reviewed and vetted against best practices. This helps us in guiding our customers on how to achieve their business goals.
Now, you should be able to define AEM as a Cloud Service and you should also be able to explain the benefits AEM as a Cloud Service. Thank you for watching this video. Have a great day. -