Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

Sling Distribution, as opposed to Replication Agent

Avatar

Level 10

Hi all,

 

AEM as a Cloud Service - ACS uses Sling Distribution, as opposed to Replication Agents to move content.

What is the benefit of this?

It must be a achieving something that Replication Agents could not,

 

Appreciate all your responses.

 

Thanks,

Rama.

 

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@AEM_Forum 

 

SCD (Sling Content Distribution) is an API-driven method for content distribution that governs the transmission of content between various sling instances. Following are some key advantages of opting for SCD over Agent Replication:

1. In SCD, distribution occurs from one or more source instances to one or more target instances, whereas in Agent Replication, the setup of multiple replication agents is required.

2. In SCD, the sync distribution facilitates the synchronization of content across multiple publishers under the control of the author instance. Such use cases, where data synchronization across numerous publishers is needed, may not be easily achievable through Agent Replication. This is crucial for AEMaaCS for supporting Blue-Green deployment model, automatic upscaling etc.


Aanchal Sikka

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

@AEM_Forum 

 

SCD (Sling Content Distribution) is an API-driven method for content distribution that governs the transmission of content between various sling instances. Following are some key advantages of opting for SCD over Agent Replication:

1. In SCD, distribution occurs from one or more source instances to one or more target instances, whereas in Agent Replication, the setup of multiple replication agents is required.

2. In SCD, the sync distribution facilitates the synchronization of content across multiple publishers under the control of the author instance. Such use cases, where data synchronization across numerous publishers is needed, may not be easily achievable through Agent Replication. This is crucial for AEMaaCS for supporting Blue-Green deployment model, automatic upscaling etc.


Aanchal Sikka