Orchestrating Multi-Site Architecture in Drupal 11
Strategies for managing shared configuration and distinct content across global enterprise instances, without the operational drag of a 2015-era multisite.
Why multi-site still matters
For many global enterprises, a fleet of country sites is a non-negotiable requirement. What has changed is the tolerable operational overhead.
The shared-config pattern
Instead of one codebase with N settings files, I prefer a shared install profile that exports a baseline content model, then selectively overrides per-site via configuration splits.
Where it breaks
Translation workflows, media library reuse, and editorial access control are the three places where the pattern pays for itself or collapses under its own weight.
Read next
- May 25, 2026
Stop Making Users Pay for Work Your CI Pipeline Could Do
Most slow Drupal sites are not slow because the code is wrong. They are slow because expensive work runs at request time when it could have run in the CI pipeline instead. Cold caches, image derivatives, search indexes. The pattern repeats. The fix is the same in every case: move the cost off your users and onto a controlled environment where nobody is waiting. This is a principle, not a tip. Three examples below to make it concrete.
- May 15, 2026
Drupal Got Cache Invalidation Right. The Rest of the Industry Is Catching Up.
Drupal's cache tag system is one of the better-designed cache invalidation models in modern web frameworks. A practitioner's look at why it works, where it breaks across system boundaries, and the mental model that travels to any stack.
- May 11, 2026
Drupal's Queue API is the Most Underused Feature in Core
Most Drupal teams reach for cron, Batch API, or external job runners when Queue API would solve the problem with less code and fewer moving parts. Three patterns where Queue API earns its place, with snippets and architecture diagrams.