AEM (Adobe Experience Manager )

 AEM as Cloud Service

• update in September 2021, Adobe Experience Manager (AEM) as a Cloud Service is a cloud-based content management system offered by Adobe.
• AEM (Adobe Experience Manager) as a cloud service refers to a cloud-based offering of Adobe Experience Manager, which is a comprehensive content management system (CMS) and digital experience platform.
• AEM as a cloud service provides a scalable, secure, and flexible environment for creating, managing, and delivering digital experiences across various channels, such as websites, mobile apps, and more.

What is new in architecture of AEM as Cloud Service?

• A dynamic architecture with a variable number of image.
• Automatic updates always latest.
• Is scaled based on the actual traffic & 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.
• Binary less replication is the default.
• AEM as a cloud service currently supports Azure.
• AWS supports is a roadmap item.
• The default workflow DAM asset update in previous version of AEM is no longer available.
• No Custom replication agents & No Reverse replication agents are allowed in AEM as a cloud.
• Many tasks have been automated ,i.e: indexing, backup etc.

CMS(Content Management System)

CMS(Content Management System)

• A Content Management System used to create, edit, organize and publish content(It is basically pages).
• CMS helps organizations to manage digital content(It is basically digital assets means images, videos, audio, dam).
• CMS help user to create, manage, and modify content on a website without the need for specialized technical knowledge.

Feature of CMS

• Provide most of the infrastructure.
• Reusability.
• create and publish content.
• No technical expertise needed for content.

Types of CMS

Traditional CMS

• A traditional CMS, like WordPress, is an all-in-one system that provides the backend (where you manage the content) and the frontend (how the content gets displayed to the user in their browser). 
• Traditional CMS platforms are designed in a way where the frontend and backend are tightly integrated.

Challenge with Traditional CMS

• Reusability we will not be able to reuse the content across different channel or front-end.
• Because Front-end and content management is bundled in a single system. 

Traditional categories in Two Parts

1. Coupled CMS

• When your logic your functionality is binded to your rendering framework that is called coupled CMS.
• A coupled CMS enables users to create and edit content then make it live to end users through the frontend attached to the CMS.
• The content authoring system and backend database are tightly coupled together.
• WordPress and Drupal are excellent examples of a coupled CMS.

  2.Decoupled CMS

• It is managed through Single CMS Platform.
• Backend and Frontend is decoupled and integrated through API.
• Backend and Frontend decoupled in different system.
• for eg: WordPress, Drupal.
• WYSIWYG editors or templates.

 Headless CMS

• Offer the backend for content storage and management.
• The result is a next-gen system built for flexibility and scalability.
• The content is then accessible via a RESTful API or GraphQL API for display on any device.
• Here, the "head" refers to the frontend—the part of the system that displays the content to users, including the website's layout, design, and user interface. and less means absence it means Frontend part is not available in Headless CMS.
• So, we can use any frontend technology for eg:- React, Angular etc.
• for eg: contentful, content stack.

Hybrid CMS

• It provides Headless functionality as well as it behave as a  Traditional CMS.
• The frontend can be separated the backend by an API.
• It is combination of Frontend + Backend + API.
• WYSIWYG editors or templates for enhanced authoring.
• for eg: AEM, dotCMS.

Difference b/w Headless and Hybrid CMS

How AEM (Adobe Experience Manager) support Hybrid architecture? 

• In a Headful or full stack model, the content is managed in the AEM repository and AEM components based on Java, HTL , etc .are used to render the content for the user experience.
• In a headless model, the content is managed in the AEM repository but delivered via APIs such as REST API and GraphQl to another system to render the content for the user experience.
• Delivers content either as fully formatted HTML or Json over the HTTP APIs.

Thanks 

Matri Sharma