AEMCS Based System Architecture Design

Question

Hi all,

How do we do an AEMCS Based System Architecture Design?

Let us say, it is not migration from AEM 6.5 or so to AEMCS, but a green field implementation.

I am aware it is a vast subject itself!

But, at a high level, what are the ten-fifteen key ingredients we consider for doing this design?

For example, we can say Fitting “Fastly” as CDN as an out of box option or our own CDN like Akamai.

Pros and Cons?

CDN is kind of Hardware decision.

Kindly cover software aspects also like Editable Templates, Separation of Mutable and Immutables, using Cloud Manager for all deployments, etc, etc.

Highly appreciate all your replies and guidance.

Thanks,

RK.

EstebanBustamante · Accepted Answer

Adobe already provides many built-in patterns and best practices that help keep your implementation aligned with recommended standards — especially around editable templates and the separation of mutable and immutable resources.

As long as you start with the latest AEM archetype, you’ll notice it includes predefined structures, validations, and guardrails that help you stay compliant with AEM as a Cloud Service best practices.

For a fresh (greenfield) project, I would recommend considering:

Git Repository Strategy: Define whether your organization will use its own Git repository integrated with Cloud Manager or rely on Adobe’s managed repository with a synchronization process. https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/cloud-manager/byogithub
Architecture Approach (Headless vs Headful vs Hybrid): Clearly determine whether the solution will be headless, traditional (Sites-based), or hybrid. This foundational decision influences frontend implementation, caching layers, content modeling, integration patterns, and overall system scalability
Technology Choice (Traditional AEM vs Edge Delivery Services): Decide whether the project will use traditional AEM Sites or Edge Delivery Services (EDS). If selecting EDS, you must also define the authoring model, such as Document-based Authoring or Universal Editor, as this affects both business user workflows and development patterns. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/edge-delivery/overview
Integration Architecture: Define how external systems will integrate with AEM, whether through REST APIs, GraphQL, or event-driven patterns.
Environment Strategy: Establish the required environments for your use case, such as multiple development environments, QA, staging, production, and Rapid Development Environments (RDEs)
Cache Strategy: Define different cache layers will operate together, including TTL settings, cache invalidation mechanisms, and overall caching hierarchy. A well-designed caching strategy is critical for performance, scalability, and cost optimization in AEM as a Cloud Service. https://meticulous.digital/blog/f/aemaacs-caching-strategy-ttl-vs-invalidation?blogcategory=Caching
Content Strategy: Determine when to use Content Fragments versus Experience Fragments and ensure alignment with the chosen architectural direction
Query and Indexing Strategy: If repository queries are required, follow best practices to avoid traversal queries, ensure proper indexing, and validate performance impact. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/query-and-indexing-best-practices
Content Model and Structure: Establish taxonomy, naming conventions, MSM strategy, and multilingual support from the start.
Governance and Permissions: Clearly define roles, permissions, authoring responsibilities, workflows, and content lifecycle management processes. https://experienceleague.adobe.com/en/perspectives/user-group-and-permission-best-practices-for-aem-assets