AEM Dispatcher Series 1 - A Developer’s Guide to What It Is and Why You Should Care
Learn about the AEM Dispatcher in perspective of developer, why it exists, and how it works as both a caching and security layer.
Performance
AEM Dispatcher Series 2 - Understanding the `dispatcher.any` File
A detailed walkthrough of the dispatcher.any configuration — explaining its key sections like /cache, /filter, /renders, and /farm. Learn how to read, structure, and maintain it properly.
AEM Dispatcher Series 3 - Securing Your AEM Site - Deep Dive into Dispatcher `/filter` Rules
A detailed walkthrough of the Dispatcher `/filter` Rules
AEM Dispatcher Series 4 - A Developer’s Guide to Dispatcher `/cache` Rules
A detailed walkthrough of the Dispatcher `/cache` Rules
AEM Dispatcher Series 5 - When and How to Clear Cache
Understand how AEM keeps cache fresh using the .stat file mechanism. Learn when and how Dispatcher marks content as stale, what /statfileslevel does, and how asset updates trigger invalidation.
AEM Dispatcher Series 6 - Handling Vanity URLs, Sessions, and `/renders`
Dive deeper into advanced setup — connecting Dispatcher to multiple Publish instances, handling logged-in users securely, and implementing vanity URLs using Apache rewrites.
AEM Dispatcher Series 7 - Dispatcher Troubleshooting
A practical guide to fixing common Dispatcher problems — stale pages, 403/404 errors, and caching issues. Learn how to read logs, test configurations, and debug step by step.
AEM Dispatcher Series 8 - Top 15 Interview Questions
The most common interview and practical questions around AEM Dispatcher. Perfect for refreshing concepts or preparing for real-world discussions.
Most Common Things AEM Developers Ignore When Using Query Builder and SQL2 Queries
Most AEM performance issues stem from inefficient query usage. This post explains when to use Query Builder vs SQL2, highlights common mistakes like missing indexes, fetching too much data, and running queries in loops, and provides practical best practices for optimized, scalable, and memory-safe queries in asset-heavy projects.