Drupal Queue API Architecture Note: Reliable Background Jobs Without a Broker
How to design background job processing in Drupal using the Queue API: minimal worker setup, trust boundaries, operational checks, and when to move to an external broker.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
How to design background job processing in Drupal using the Queue API: minimal worker setup, trust boundaries, operational checks, and when to move to an external broker.
Drupal's Cache API lets you invalidate precisely with cache tags and contexts instead of clearing all caches. Learn how to attach #cache metadata to render arrays, avoid stale content, and keep hit rates high.
Content type or custom entity? A practical decision framework for Drupal's Entity API, with a worked inspection-record example, EntityQuery usage, and honest trade-offs.
Learn how to set a config sync directory outside the web root, export and import Drupal configuration with Drush, and avoid common pitfalls.
Drupal's JSON:API module has shipped in core since 8.7, exposing every entity type as a spec-compliant RESTful API with filtering, pagination, sparse fieldsets, and compound documents — zero custom controllers required. Covers a fetch example, access control, cache tags, and production limits.
Use Drupal Configuration Split with settings.php to layer environment-specific modules on a shared base config. Worked example: dev split for devel and stage_file_proxy, activation per environment, avoiding UUID mismatches and secrets in YAML.
Learn how Drupal’s Layout Builder lets editors assemble pages via drag‑and‑drop while keeping layouts as version‑controlled configuration, plus a worked product‑landing‑page example and key trade‑offs.
Learn how to use the Drupal Views module to create dynamic, filterable content lists with pagination and contextual filters to improve site navigation and performance.
An architecture note on Drupal's render cache: the requirements it must meet, the smallest design that works, trust boundaries around contexts and tags, operational checks, and when to change the design.