Cache management in any web content management implementation has been one of the most important aspects driving performance and response times of a website. In this article, my efforts will be to present a rather unconventional approach to control caching and the rationale behind it.
What is dispatcher?
Dispatcher is very diverse in itself, in a textbook style definition of dispatcher in context of AEM (Adobe Experience Manager) would be,
Dispatcher is Adobe Experience Manager’s caching and/or load balancing tool.
It is an HTTP server on top of AEM Publisher (or author), which helps in handling the content rendering more elegantly. Some important functionality it provides are mentioned below -
1. storing (or “caching”) as much of the site content as is possible,
2. load-balancing for better fail-safe coverage,
3. accessing the publisher server as little as possible,
4. adds a layer of security on the server to prevent any attacks.
Now that we know what dispatcher means, let’s try to explore its basic working mechanism.
Below is one of the very famous flow diagram which we come across very often in any standard official document.