Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

An Introduction to the Architecture of Adobe Experience Manager as a Cloud Service | AEM Community Blog Seeding

Avatar

Administrator

BlogImage.jpg

An Introduction to the Architecture of Adobe Experience Manager as a Cloud Service by Adobe

Abstract

Adobe Experience Manager (AEM) as a Cloud Service has resulted in changes to the architecture.

Scaling
AEM as a Cloud Service now has:

A dynamic architecture with a variable number of AEM images.
Dynamic architecture

This architecture:

Is scaled based on the actual traffic and actual activity.

Has individual instances that only run when needed.

Uses modular applications.

Has an author cluster as default; this avoids downtime for maintenance tasks.

This enables autoscaling for varying usage patterns:

Autoscaling for varying usage patterns

To achieve this, all instances of the AEM as a Cloud Service are created equal, each with the same default sizing characteristics in terms of the number of nodes, allocated memory and allocated computing capacity.

AEM as a Cloud Service is based on the use of an orchestration engine that:

Constantly monitors the state of the service.

Dynamically scales each of the service instances as per the actual needs; both scaling up or down as appropriate.

This:

Is applicable to the number of nodes, the amount of memory and the allocated CPU capacity on each node.

Allows AEM as a Cloud Service to accommodate your traffic patterns as they change.

Read Full Blog

An Introduction to the Architecture of Adobe Experience Manager as a Cloud Service

Q&A

Please use this thread to ask the related questions.

0 Replies