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

Architectural changes or improvements in AEM as a Cloud Service | AEM Community Blog Seeding

kautuk_sahni
Community Manager
Community Manager

BlogImage.jpg

Architectural changes or improvements in AEM as a Cloud Service by Aemtutorial

Abstract

Architectural changes or improvements in AEM as a Cloud Service
Below given the noted architectural changes in AEM as a cloud service
--->Scaling - A dynamic architecture with a variable number of AEM images.
--->Has an author cluster as default;
--->Has individual instances that only run when needed.
--->Dynamically scales each of the service instances as per the actual needs; both scaling up or down as appropriate.
--->Many tasks have been automated. - like indexing , backup etc, binary-less replication is the default.
--->Micro-services sharing the processes which were done by core AEM itself: For eg: Heavy-load tasks, such as queues, jobs and bulk-processing tasks etc
--->Authoring UI is purely touch-enabled; the classic UI is no longer available
--->AEM as a Cloud Service currently supports Azure. AWS support is a roadmap item.
--->The default workflow DAM Asset Update in previous versions of AEM is no longer available.
--->No Custom replication agents & No Reverse Replication Agents are allowed in AEM as cloud

Read Full Blog

Architectural changes or improvements in AEM as a Cloud Service

Q&A

Please use this thread to ask the related questions.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

0 Replies