Reimagining Replication Agents on AEM as a Cloud Service | AEM Community Blog Seeding

[kautuk_sahni]

Reimagining Replication Agents on AEM as a Cloud Service by Damian Langsweirdt

Abstract

Part of the journey when evaluating how to migrate to AEM as a Cloud Service involves taking a look at your current AEM implementation to see if there are any incompatibilities or areas which will require refactoring. This may include reviewing documentation, code, and running the Best Practices Analyzer (BPA) tool. One area which may be highlighted during your review is replication agents.

In the pre-Cloud Service model, numerous situations called for replication agents. This article won’t cover all use cases, but you can read more background here. With Cloud Service and its new architecture, the rules have changed in this area. Read on for some tips on navigating this change.

Author to Publish
For standard publishing, or copying content from an author environment to a publish environment, this is handled out-of-the-box with Cloud Service — no custom agents required. See here.

Publish to Author
Sending content from a publish environment back to an author environment is known as reverse replication. This is not supported per the Notable Changes documentation. Pre-Cloud Service, this is typically (although not exclusively) done for one of two reasons.
The first reason is to support user-generated content (UGC). The alternative with Cloud Service is to externalize UGC out of AEM. Let AEM focus on managed content delivery, and treat UGC as an integration.

Read Full Blog

Reimagining Replication Agents on AEM as a Cloud Service

Q&A

Please use this thread to ask the related questions.