Can we enable dispatcher caching on author AEM as a Cloud?

Hi @abhishek_narula25 ,

The Adobe Experience Manager (AEM) Dispatcher is typically used on the publish instance rather than the author instance.

1. Author Instance: This is the environment where content authors and editors create, modify, and manage content. It is not typically exposed to the public internet. Caching mechanisms on the author instance are generally limited to optimizing the authoring experience and do not have the same emphasis on content delivery as the publish environment.

2. Publish Instance: This is the environment where content is published and made available to the public. The publish instance is responsible for serving content to end-users. The Dispatcher is often installed on the publish instance and is configured to cache and deliver static content, reducing the load on the AEM instance and improving response times.
   
   

Also, as mentioned in the link you will need to install docker in order to do a local testing

Hi @abhishek_narula25 

In AEM as a Cloud Service, there is no dispatcher for author, instead there is a Adobe Managed CDN for the same purpose. Please refer this document for details on architecture on how its setup - https://experienceleague.adobe.com/docs/experience-manager-learn/cloud-service/caching/author.html?lang=en#:~:text=It%20caches%20immutable%20files%2C%20such,TTL%20on%20custom%20Client%20Libraries.

Thanks

Narendra

Hi Abhishek,

In AEM as a Cloud Service you probably want to utilise Preview Service[1] this way you will show Authored content to any interested party before it goes to Live.

Preview has standard Publisher to render content and Dispatcher to cache content.

[1] https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/sites/authoring/fundamentals/previewing-content.html?lang=en

Regards,

Peter

@abhishek_narula25 - Yes, caching on AEMaaCS is supported

Please refer to below docs - 

Caching AEMaaCS

Also for cache invalidation - 

Hope this helps!

Hi @abhishek_narula25 

As pointed out by @narendragandhi, the Author service lacks a dispatcher, making it impossible to customize your cache strategy. Additionally, the article he shared clearly emphasizes that this approach is discouraged[1]. It seems there might be a misunderstanding regarding the purpose of Author, Publisher, and Preview instances. If you are implementing a headless solution, it is advisable to consume data from a publisher instance (either preview or publish), as mentioned by @Peter_Puzanovs. If your goal is to test before publishing, consider exploring concepts like different environments or utilizing the preview functionality.

I hope this clarifies your question to some extent

[1]. 

@abhishek_narula25 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.