Sling Distribution, as opposed to Replication Agent | Community
Skip to main content
AEM_Forum
New Participant
October 29, 2023
Solved

Sling Distribution, as opposed to Replication Agent

  • October 29, 2023
  • 1 reply
  • 1489 views

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.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by aanchal-sikka

@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.

1 reply

aanchal-sikka
aanchal-sikkaAccepted solution
New Participant
October 29, 2023

@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