In preparation for Adobe Summit week, I sat down (well socially-distanced, unfortunately!) with two colleagues at ICF Next to discuss the future of AEM in the cloud. We give some context for folks to inform their decision-making process on whether or not it’s a good time to move their marketing workloads to AEM as a Cloud Service. And, if not, what their current strategy should be.
As covered in other posts on AEM as a Cloud Service, this is a pivotal time in marketing website infrastructure and project planning. For the first time, it’s technically possible (though maybe or maybe not recommended) to have an enterprise-grade experience management platform running your site entirely in a managed cloud services. There are a lot of important things to know about whether or not your Adobe-powered internet properties should move to cloud services, and it’s not a black-and-white proposition at all.
In this podcast, we discuss:
- What AEM as a Cloud Service consists of
- A basic explanation of AEM architecture, explaining the differences between self-managed AEM hosting in the cloud, and AEM as a Cloud Service
- Diagrams of both infrastructure paradigms
- What you need to know about Continuous Integration and AEM as a Cloud Service
- How AEM as a Cloud Service affects maintenance and the workload on your DevOps personnel
- How AEM as a Cloud Service makes use of the AEM Desktop App less terrifying for your Sys Admins
- Whether or not you need to be on AEM 6.5 before attempting to migrate to AEM as a Cloud Service
- Limitations and gotchas of running AEM as a Cloud Service, including log aggregation (Splunk, etc) and Application Performance Monitoring (APM).
Speakers in this podcast are:
- Tad Reeves, AEM Architect focused on infrastructure and DevOps
- Eric Van Geem, AEM Technical Architect and developer
- Fred Faulkner, ICF Next Partner, Strategic Alliances
Please give the video a watch, and let us know what other questions you have on the new AEM cloud offerings, and we’d love to do another podcast segment to cover them!
Leave a Reply