Adobe Experience Manager (AEM) is a platform for building websites, mobile apps, and forms. It combines a content management system with a digital asset management system, letting teams manage their entire digital presence from one place.

At its core, AEM is built on three key technologies: the Java Content Repository (JCR), the OSGi framework, and the Apache Sling web framework. Think of them as the foundation, the engine, and the delivery system of a car. Each part has a distinct job, but they work together to create a powerful and flexible platform.

Everything in AEM is stored in the Java Content Repository, or JCR. The best way to picture the JCR is as a highly organized digital library. Instead of books, it stores content as a tree of nodes. Each node can have properties, like a title or an author, and can also have other nodes nested underneath it.

A webpage, for instance, is a node. Its child nodes might be the different components on the page, like text blocks, images, and videos. The image component node would have a property pointing to the actual image file, which is also stored as a node elsewhere in the repository. This hierarchical structure makes it easy to manage complex content relationships.

AEM uses an OSGi framework to manage its code. OSGi is a system for building applications out of small, independent modules called "bundles." It's like building with LEGO bricks. Each brick is a self-contained unit with a specific function, but you can snap them together to create something much larger and more complex.

This modular design is one of AEM's biggest strengths. Bundles can be installed, started, stopped, and updated individually without needing to restart the entire application. If you need to add a new feature, you can deploy it as a new bundle without affecting the rest of the system. This makes AEM stable, flexible, and easier to maintain.

Apache Sling is the web framework that connects content requests to the content in the JCR. Its job is to figure out what a user is asking for and how to display it. Sling does this by breaking down a URL to find the right piece of content.

When a request like https://www.example.com/products/shoes/running.html comes in, Sling interprets the path /products/shoes/running as a direct path to a node in the JCR. Once it finds the node, Sling looks at its properties to determine which script to use for rendering the content. This script then pulls the content from the JCR node and formats it into the HTML page that gets sent back to the browser.

Sling’s content-first approach is what makes AEM so powerful. The URL itself dictates the content, not a parameter in a database query. This creates clean, meaningful URLs and a direct link between the user's request and the content they receive.

This diagram shows how a request flows through the system. Sling acts as the traffic controller, using the URL to fetch content from the JCR, engaging OSGi services for any required logic, and finally using a script to assemble the page.

While AEM is powerful software, running it effectively requires a robust infrastructure. This is where AEM Managed Services comes in. Instead of hosting AEM on your own servers, Adobe hosts and manages it for you in the cloud.

This service handles tasks like server maintenance, security patches, backups, and performance monitoring. It ensures the system can scale automatically to handle sudden spikes in traffic without crashing. By offloading these operational burdens, teams can focus on what they do best: creating and delivering compelling digital experiences.

Now let's review these foundational concepts.

Understanding these core components—JCR for content, OSGi for modular logic, and Sling for delivery—is the first step to mastering AEM.