What is the idea way to bring content from Publish to Author in AEMaaCS

[Prithwiraj_Deb]

How to I bring content from Publish to Author instance (Use Cases brining user generated content) back to author instance in AEMaaCS? 

Replication Agent? Any best practice? 

[chavad]

Hi @Prithwiraj_Deb 

You can try ACS commons content sync tools. Works well for syncing content from publish to author. More details - https://adobe-consulting-services.github.io/acs-aem-commons/features/contentsync/index.html

Never tried with UGC though.

[Prithwiraj_Deb]

How about sling reverse replication as a method ? 

https://medium.com/@toimrank/aem-replication-and-reverse-replication-ebaf0f5f322c

[narendiran_ravi]

In AEM as a Cloud Service (AEMaaCS), reverse replication is not supported. You can refer to the official documentation for more details: AEM Cloud Changes - Replication Agents.

• Not sure how the content gets synched between different publish pods.
• Third-Party Solutions: If you need to implement features like ratings and reviews, consider using third-party solutions such as Trustpilot or Bazaarvoice. These platforms specialize in managing user feedback and can integrate seamlessly with AEM, providing reliable alternatives for user-generated content.

[Prithwiraj_Deb]

sling reverse is applicable in AEMaaCS

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aemaacs-sling-content-dist...

https://sling.apache.org/documentation/bundles/content-distribution.html

[Tethich]

I believe there is confusion around terms. Replication is a word used when we talk about AEM on-prem. When we talk about AEMaaCS the wording is distribution. So you both may be right.

@Prithwiraj_DebBut is seams that the documentation talks really clear about hot to set up SRD:

• on target instance: one reverse agent:

org.apache.sling.distribution.agent.impl.ReverseDistributionAgentFactory-reverse.json
name="reverse"
packageExporter.endpoints=["http://localhost:4503/libs/sling/distribution/services/exporters/reverse"]

• on source instance: one queue agent and one exporter for that agent

org.apache.sling.distribution.agent.impl.QueueDistributionAgentFactory-reverse.json
name="reverse"

org.apache.sling.distribution.packaging.impl.exporter.AgentDistributionPackageExporterFactory-reverse
name="reverse"
agent.target="(name=reverse)"

Have you tried it and is not working for you ?

Some addition materials that may help you:
https://aemtechblog.medium.com/content-distribution-in-aem-as-a-cloud-service-d457b390f8f9
https://medium.com/tech-learnings/sling-content-distribution-in-aem-part-2-3a66933be45d

[Jörg_Hoh]

In AEM CS you cannot use content distribution or replication to get content from publish to author; this pattern is not supported.

[daniel-strmecki · Accepted solution]

Hi @Prithwiraj_Deb,

personally, I consider content backflow a bad architectural pattern and a relic from the past. I would strongly suggest looking for 3rd party solution or building your own microservices for storing and delivering user-generated data.

Good luck,

Daniel

[Saravanan_Dharmaraj]

@Prithwiraj_Deb I agree with Daniel. UGC should be stored in common data store like Mongo to be accessible from both Author and Publish instances or consider using third party products like Lithlum or salesforce to store UGC.