AEM | Adobe Managed Services vs. Self-Hosting AEM – Pros & Cons | AEM Community Blog Seeding

AEM | Adobe Managed Services vs. Self-Hosting AEM – Pros & Cons by TAD REEVES

Abstract

What is Adobe Managed Services and how is it different from hosting it myself?
Let’s get the basics out of the way first. How does Adobe Managed Services (AMS) differ from self-hosting?

A simplified diagram of Adobe Managed Services and how you interact with AEM, and what functions you do not have access to.
The above is a simplified view of what Adobe Managed Services offers. From an infrastructure perspective, Adobe provides a simplified GUI front-end that allows them to essentially provision and own AWS or Azure accounts (your choice) where your AEM environment will be deployed to, and then they provision and maintain whatever size of AEM environment you are licensed for in your AMS contract. Starting and stopping environments can be done self-service-style via their Cloud Manager web front-end. Technical staff at AMS then handle any platform issues that come up with your environment, and are the only ones who have back-end access to ssh to your instances, to look at Splunk or New Relic to get application performance data, and to view or modify the automation that creates your environment. Much more on that to follow.

From what Adobe has said at the last few Adobe Summits, they’ve designed their AMS offering around “the 80th-percentile use cases” to try to make a system that works for as many use cases as possible, while enabling clients to run an AEM system with less devops staff than in a more traditional model. As model that was designed to be fairly self-service, it comes with its own inherent advantages and disadvantages, as well as company personas that work, and ones that do not.

Read Full Blog

AEM | Adobe Managed Services vs. Self-Hosting AEM – Pros & Cons

Q&A

Please use this thread to ask the related questions.