AEMaaCS Sling Content Distribution capability

[AEM_Forum]

Adobe documentation at Introduction to the Architecture of Adobe Experience Manager as a Cloud Service | Adobe Experience M... says:

"Adobe Experience Manager as a Cloud Service has modified the way publishing content works. 

AEM as a Cloud Service now uses the Sling Content Distribution capability to move the appropriate content."

1. Why so? Why not the traditional (On Prem) publishing process?

If Assets Binary Cloud is one and the same for all author and publish instances, do we need to publish assets? Publishing pages alone should be good enough.

2. For reverse replication also the same (Sling Content Distribution) is true?

Appreciate all your responses.

Thanks,

Rama.

[nitesh_kumar]

Hi @AEM_Forum ,

SCD has been introduced because fundamentally AEMaaCS is different from On-premises, so it's not comparable.

1. Why so? Why not the traditional (On-Prem) publishing process? - because AEMaaCS instances are short-lived (meaning they are created/destroyed frequently) there is a concept of Golden master was introduced, which subscribes to the replication queue. you can find more details here

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/overview/architectu... 

AdapTo conference - https://www.youtube.com/watch?v=kKLbS7h-4IY

2.) For reverse replication also the same (Sling Content Distribution) is true? - AFAIK, reverse replication is not supported on AEMaaCS.

Hope this helps, let me know if you have further questions.

Regards,

Nitesh

[AEM_Forum]

Thanks Nitesh.

Reverse replication is not supported on AEMaaCS.

What has replaced reverse replication on AEMaaCS?

Or UGC through blogs and communities will not come as these (blogs and communities) are discontinued in AEMaaCS?

There is definitely a gap because of these being discontinued in AEMaaCS and how are we bridging it?

Thanks,

Rama.

[nitesh_kumar · Accepted solution]

Hi @AEM_Forum ,

AEM Communities is not supported on Cloud, and AFAIK it's not on the roadmap as well.

There is no replacement for reverse-replication, for those cases and UGC, the recommended way is to keep it externally (Database), so that publisher and the author can read the same data.

It was designed this way because Cloud Architecture is different from the on-premise version, Customers can still opt for an AMS-based/On-premise setup that has AEMClassic (6.5) if they have the requirement.

https://experienceleague.adobe.com/docs/experience-manager-65/communities/introduction/overview.html... 

Regards,

Nitesh

[Mani_kumar_]

Adding to @nitesh_kumar as said binary storage is common and if you want Metadata to be sync you have to publish the assets and as it follows topology based architecture we need all the pods to be sync