Dispatcher Tips and Tricks on AEM as a Cloud Service | AEM Community Blog Seeding

Avatar

Avatar

kautuk_sahni

Community Manager

Total Posts

5.8K

Likes

1.0K

Correct Reply

1.1K

Avatar

kautuk_sahni

Community Manager

Total Posts

5.8K

Likes

1.0K

Correct Reply

1.1K
kautuk_sahni
Community Manager

01-02-2021

BlogImage.jpg

Dispatcher Tips and Tricks on AEM as a Cloud Service by Damian Langsweirdt

Abstract

Content delivery using Adobe Experience Manager (AEM) has long been aided by the dispatcher module, which sits in between visitors to a website and AEM itself to help with caching, URL rewriting, HTTP header manipulation and more. Those benefits generally carry over from the traditional AEM platform to AEM as a Cloud Service, however as a member of the Cloud Service engineering team at Adobe I wanted to share some insights to best take advantage of the power of the dispatcher on Cloud Service based on learnings from real customer implementations.

Tip #1 — Use the local dispatcher validator
One difference with Cloud Service is the requirement that all dispatcher configuration is treated as code stored in git, and deployed via the standard Cloud Manager CI/CD pipeline. A side of effect of this difference is that small, iterative changes made during development require a more time-consuming deployment, right? Not necessarily! See the documentation which describes how much of the changes can be validated and tested locally without requiring a cloud deployment.

Read Full Blog

Dispatcher Tips and Tricks on AEM as a Cloud Service

Q&A

Please use this thread to ask the related questions.

AEM AEMEBlogSeeding Experience Manager