Acquia Developer (D10) case studies
Acquia Developer (D10) · Put your knowledge to work in context.
The Acquia Certified Drupal 10 Developer credential is a professional certification aimed at developers who build and maintain Drupal 10 sites and who want independent, third-party validation of their skills. It is intended for working developers - typically those with hands-on experience writing custom modules and themes and configuring Drupal site architecture - rather than for beginners or for purely editorial users. The Acquia Developer (D10) case studies are 5 cases and about 1,941 words.
1Editorial site with a caching and stale-content complaint
A Drupal 10 site runs on Acquia Cloud with Varnish in front of three web nodes. Editors report that a promoted article's updated teaser on the home page still shows the old summary for about 10 minutes after saving, but the article's own detail page is correct immediately.
418 words, about 2 min2Config sync drift between local and Acquia environments
A team deploys Drupal 10 to Acquia Cloud using a pipeline that runs drush config:import on each deploy. Local development uses config split with a local split enabling devel and stage file proxy, and a prod split enabling only Acquia modules.
350 words, about 2 min3Slow anonymous page loads after enabling a contributed module
A marketing site on Acquia Cloud (2 web nodes, Varnish, memcache) serves 200,000 anonymous page views/day. After adding a contributed module that renders a "recently viewed" block, anonymous TTFB rises from 180 ms to 900 ms and the Varnish hit ratio drops from 85% to 40%.
354 words, about 2 min4Field storage decision for a high-cardinality attribute
A product catalogue needs a sku string (max 64 chars, unique, frequently filtered and sorted), a description (long text, rarely filtered), and a specifications array of key/value pairs (up to 40 pairs per product, each key unique per product, values up to 255 chars). The site has 500,000 products imported nightly.
409 words, about 2 min5Permission model for a multi-site editorial workflow
A publisher runs one Drupal 10 codebase serving three sites via a multisite configuration. Editors on site A must not see content from site B, but a shared "newsroom" role must be able to publish to all three.
410 words, about 2 min