Yesterday, Cedric Huesler, the Director of Product Management at Adobe started a Twitter thread on AEM as a Cloud Service. I have a number of burning questions about AEM as a Cloud Service, so I figured I’d take Cedric up on the offer to ask anything.
Cedric graciously replied, hopefully, you find these replies helpful as we all learn more about AEM as a Cloud Service:
Q1. What’s the plan for customers who do not want to run this in Adobe’s tenant?
A1. Today we are offering AEM as CS, MS and self-hosting. We have a single code base for all three.
Q2. What is the roadmap for AEM “Classic”?
A2. We will update SP schedule later this week.
A2 (part 2). SP schedule updated with 2020 dates: https://helpx.adobe.com/experience-manager/maintenance-releases-roadmap.html
@WimSymons – Not really an answer. Okay there will be extra SP’s and CFP’s, but the question is, will there any “classic” AEM major releases after 6.5 or will you put your money on AEM in the cloud only?
A2 (part 3). For 2020, we keep updating the single code base for the 3 deliverables and don’t see a need for a major release (to avoid efforts on customer-side to move up – SP are easier to install). If you are not yet on 6.5 – please do that 1st
Q3. What’s the underlying persistence mechanism? S3+Mongo?
A3. See Oak code-base – mongo and new segment blob store.
Q4. Is this running on Azure? AWS? Will customers be able to choose?
A4. It’s a mix – mostly azure today but can change anytime.
Q5. Will customers be able to choose what AZ’s to deploy their instances? Including China?
A5. Yes, today you can choose regions.
Q6. Will Customers be able to specify routing rules for requests based on the visitors origin?
A6. Yes, CDN is bundled in.
Q7. Can you temporarily skip / roll back releases if you encounter problems?
A7. Yes and No, the release validation process does that – automated.
Q8. How often will Adobe ship new releases and what will be the procedure to validate customer images?
A8. Daily, validation process is quite evolved. Will link up details later
Q9. What’s the index storage mechanism? SOLR?
A9. Today unchanged.
Q10. Is there a plan / timeline to port the remaining AEM apps (Screens, Forms) to AEM as a Cloud Service?
A10. Yes – this year.Huesler, Cedric (@keepthebyte). “1216857162405707777” 13 Jan 2020 Tweet.
Do you have your own questions about AEM as a Cloud Service? Ask Cedric yourself!
Additional Insights on AEM as a Cloud Service
A few of the underlying technologies which Cedric references or are useful to read:
Digitizing the Healthcare and Patient Experience
Find out how more than 100 healthcare executives and their respective organizations are modernizing patient and customer experiences.
The new provisioning model for Apache Sling which is used to generate AEM as a Cloud Services instances by creating a “feature model” with the base AEM and customer code. You can also watch the 2019 AdaptTo seminar on the Sling Feature Model.
The Oak Blob Store is the new persistence mechanism for large binary files. It splits the files into chunks, hashes each chunk and then stores each chunk into the segment store.
Seminar from AdaptTo 2019 talking about Adobe’s deployment of AEM in Kubernetes (aka AEM as a Cloud Service).
Another seminar from AdaptTo 2019, talking about how Adobe uses Apache Kafka to orchestrate Content Distribution on AEM as a Cloud Service.
The starting point for Adobe’s documentation on AEM as a Cloud Service.
Adobe’s reference site WKND has been updated to be compatible with AEM as a Cloud Service.
Perficient’s ongoing blog series exploring AEM as a Cloud Service