AEM deployment

 

After Reading this article, you should have an understanding of: 

• Introduction to AEM deployment options
• AEM On-Premises Architecture
• Adobe Managed Services (AMS) Architecture
• AEM as a Cloud Service 
• Why AEM as a Cloud Service?
• Comparison between On-Premise, Managed
• Comparison between On-Premise, Managed & cloud-deployment
• Best practices for AEM deployment

Introduction to AEM deployment options

Adobe Experience Manager offers a range of deployment options to suit different organizational needs and preferences. It clearly depends on what you aim to achieve with AEM. Are you looking to build a new website, revamp an existing one, or create a personalized digital experience platform? Different deployment options have their own set of benefits and considerations, from the control and customization possible with on-premises deployment to the operational efficiency and innovation speed of AEM as a cloud service.

1. AEM on premisses
2. AMS – Adobe Managed Service (mainly hosted on AWS) 

3. AEM as a Cloud Service (AEMaaCS) 

AEM On-Premises Architecture

AEM on-premises architecture is a traditional deployment model where the AEM instances are hosted within an organization’s own data center or on their private cloud. This model gives organizations complete control over their infrastructure, security, and compliance. 

Key Components of AEM On-Premises Architecture

• Author Instance 
• Publish Instance
• Dispatcher
• Database
• File System
• Replication Agents
• Backup and Recovery

Detailed Explanation of Components 

Author Instance 

The Author instance is where content creators, editors, and marketers work. It is used for creating, editing, and managing the content

Publish Instance

The Publish instance is responsible for delivering the content to end users. It serves the content through websites, mobile apps, and other channels

Dispatcher

Dispatcher is a caching and load-balancing tool used to increase the performance of AEM. It caches content to reduce the load on the publish instances and balances the load among multiple publish instances

Database

The database is used to store content metadata, user data, and configuration settings. AEM supports various database systems such as PostgreSQL, MySQL, Oracle, and others

• Storing content metadata and configuration
• Ensuring data integrity and consistency
• Supporting transactional operations and queries

File System

The file system is used to store binary content such as images, videos, and other digital assets. These files are usually stored in a shared storage system accessible by AEM instances