Drupal with Redis or Valkey cache backends
Moving cache, lock, flood and queue storage from the database to Redis or Valkey: configuration, memory sizing, eviction policy and high availability for the Redis service itself.

Specific caching layers and scaling components for busy Drupal sites: Redis or Memcache backends, reverse proxies and CDNs with cache tag purging, BigPipe, cron and queues, images and cache warming.
Moving cache, lock, flood and queue storage from the database to Redis or Valkey: configuration, memory sizing, eviction policy and high availability for the Redis service itself.
Using Memcached as Drupal's cache store: when it is preferred over Redis, multi-server pools, and what still lives in the database.
Putting Varnish in front of Drupal and invalidating pages by cache tag with Purge and the Varnish purger: VCL requirements, queue processing and authenticated traffic.
Caching Drupal at the edge with CDN-specific modules, purging by cache tag or URL when content changes, and setting cache lifetimes for anonymous pages.
Running cron reliably on multi-server setups: system cron or container jobs, Ultimate Cron for per-job schedules, queue workers for heavy tasks and avoiding overlapping runs.
Reducing page weight with image styles, responsive images and Image Optimize pipelines, plus generating derivatives on busy sites without overloading web servers.
Avoiding cold-cache slowdowns after releases and cache clears by warming critical pages and entities with the Warmer module, and scheduling warmers safely.
What core aggregation already does since Drupal 10.1, why the AdvAgg module is obsolete, and front-end performance work that remains in the theme.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.