Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

What are the differences between AEM as on-premise and AEM as a Cloud?

Avatar

Level 3

What are the differences between AEM as on-premise and AEM as a Cloud?

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Adobe Provide 3 types of AEM license, AEM on Prem, AMS and AEMaaCS.

 

Adobe Experience Manager (AEM) can be deployed : as an on-premise solution and as a cloud service(AEMaaCS). Each deployment option has its advantages and considerations:

 

AEM On-Premise:

  1. Control and Customization: AEM on-premise provides more control over the entire infrastructure and allows for extensive customization. Organizations can tailor the environment to their specific needs.

  2. Data Security: Some organizations, particularly those in highly regulated industries, may have strict data security requirements that make on-premise deployments more appealing. They have full control over data storage and management.

  3. Licensing: On-premise deployments often have a different licensing model than cloud services. Licensing costs can vary based on the number of servers, users, and features required.

  4. Integration: On-premise AEM can be integrated with other on-premise systems and databases within an organization's data center.

  5. Upfront Costs: Initial costs for hardware, infrastructure, and setup can be high. Organizations must manage and maintain their hardware, which may require dedicated IT resources.

AEM as a Cloud Service:

  1. Scalability: AEM as a Cloud offers scalability and flexibility. Organizations can easily scale resources up or down based on demand. Adobe manages the underlying infrastructure, ensuring high availability and performance.

  2. Managed Service: Adobe handles server maintenance, security updates, and other infrastructure-related tasks, reducing the operational burden on organizations.

  3. Faster Time to Market: AEM as a Cloud can reduce the time required for initial setup, allowing organizations to get started with their web projects more quickly.

  4. Subscription Model: AEM as a Cloud typically follows a subscription-based pricing model, which can help with cost predictability. Licensing may be more flexible, and organizations pay based on usage.

  5. Global Delivery: Cloud deployments are often distributed across multiple data centers worldwide, ensuring low-latency access for global audiences.

  6. Security and Compliance: Adobe provides robust security measures and compliance certifications. Data protection and compliance are central to cloud services.

The choice between AEM on-premise and AEM as a Cloud depends on an organization's specific needs, resources, and objectives. Some organizations may opt for a hybrid approach, where they use AEM as a Cloud for certain projects and retain on-premise solutions for others. It's important to carefully evaluate the pros and cons of each deployment option to determine which aligns best with the organization's goals and constraints.



Arun Patidar

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Adobe Provide 3 types of AEM license, AEM on Prem, AMS and AEMaaCS.

 

Adobe Experience Manager (AEM) can be deployed : as an on-premise solution and as a cloud service(AEMaaCS). Each deployment option has its advantages and considerations:

 

AEM On-Premise:

  1. Control and Customization: AEM on-premise provides more control over the entire infrastructure and allows for extensive customization. Organizations can tailor the environment to their specific needs.

  2. Data Security: Some organizations, particularly those in highly regulated industries, may have strict data security requirements that make on-premise deployments more appealing. They have full control over data storage and management.

  3. Licensing: On-premise deployments often have a different licensing model than cloud services. Licensing costs can vary based on the number of servers, users, and features required.

  4. Integration: On-premise AEM can be integrated with other on-premise systems and databases within an organization's data center.

  5. Upfront Costs: Initial costs for hardware, infrastructure, and setup can be high. Organizations must manage and maintain their hardware, which may require dedicated IT resources.

AEM as a Cloud Service:

  1. Scalability: AEM as a Cloud offers scalability and flexibility. Organizations can easily scale resources up or down based on demand. Adobe manages the underlying infrastructure, ensuring high availability and performance.

  2. Managed Service: Adobe handles server maintenance, security updates, and other infrastructure-related tasks, reducing the operational burden on organizations.

  3. Faster Time to Market: AEM as a Cloud can reduce the time required for initial setup, allowing organizations to get started with their web projects more quickly.

  4. Subscription Model: AEM as a Cloud typically follows a subscription-based pricing model, which can help with cost predictability. Licensing may be more flexible, and organizations pay based on usage.

  5. Global Delivery: Cloud deployments are often distributed across multiple data centers worldwide, ensuring low-latency access for global audiences.

  6. Security and Compliance: Adobe provides robust security measures and compliance certifications. Data protection and compliance are central to cloud services.

The choice between AEM on-premise and AEM as a Cloud depends on an organization's specific needs, resources, and objectives. Some organizations may opt for a hybrid approach, where they use AEM as a Cloud for certain projects and retain on-premise solutions for others. It's important to carefully evaluate the pros and cons of each deployment option to determine which aligns best with the organization's goals and constraints.



Arun Patidar