AEM Dispatcher is the caching and request-filtering layer commonly used in front of Adobe Experience Manager Publish environments. It helps deliver pages efficiently while protecting the publish tier from unnecessary traffic and unapproved requests.
DIGITAL INSIGHTS
AEM Dispatcher
Protect the Publish tier and improve visitor experience through controlled requests, effective caching, and reliable content freshness
Receive a request for a page or assetA visitor, application, or bot requests content through the web tier before it reaches the AEM Publish environment.
Allow only approved request patternsUse explicit rules to permit appropriate paths and methods while blocking unnecessary, unsafe, or unapproved requests from reaching Publish.
Serve eligible content quicklyReturn a valid cached response whenever possible to reduce latency and limit load on the publish environment.
Retrieve content when the cache needs itRoute permitted cache misses to AEM Publish, then store eligible responses according to the defined cache rules and delivery needs.
Keep content fresh and operations visibleRefresh affected cache entries after publishing changes and monitor hit rates, errors, response times, rule exceptions, and real user behavior.
Executive Summary
Dispatcher is a core part of many AEM delivery architectures. It improves speed through caching, supports security through request filtering, and helps teams control how content is invalidated and served after publishing changes.
What Dispatcher Does
- Caches eligible content close to the web server.
- Filters incoming requests based on approved rules.
- Routes allowed requests to AEM Publish when cache is unavailable.
- Supports cache invalidation when content is activated.
- Helps reduce load on the publish environment.
Why It Matters
Without a well-managed caching layer, public AEM sites can become slower, less resilient, and harder to secure. Dispatcher configuration directly affects page freshness, performance, troubleshooting, and the customer experience.
Best Practices
- Use explicit allowlists for request filtering.
- Document cache rules, invalidation behavior, and exceptions.
- Keep cache configuration aligned with content publishing needs.
- Test cache behavior for key pages, assets, and personalization scenarios.
- Monitor cache-hit patterns, errors, and response times.
- Review configuration during releases and platform changes.
Common Mistakes
- Using overly broad request filters.
- Serving stale content because invalidation rules are incomplete.
- Bypassing caching without a clear business reason.
- Making configuration changes without validating production behavior.
Key Takeaways
AEM Dispatcher is both a performance and security capability. Its value depends on intentional cache design, controlled request filtering, reliable invalidation, and ongoing operational monitoring.
Frequently Asked Questions
Is Dispatcher the same as a CDN?
No. A CDN can cache and distribute content globally, while Dispatcher is typically the AEM web-tier caching and filtering layer. Many enterprise architectures use both together.
