Conrad caching

Train

Conrad caching

Preparation for the caching part of the Conrad interview, written from your Conrad Caching note — HTTP cache headers and validation, Cloudflare's cache, Nitro's cache with Redis, and the cache layers of a large e-shop.
MDN HTTP cachingNitro cache (v2)Cloudflare default cache behavior

Written from your Conrad Caching note for the interview on 14 October 2026. The questions are general ones about caching, the kind an interviewer asks: how HTTP caching, CDNs and Nitro's cache work and how you would set them up for a large shop. They are not about Conrad's own configuration; the note is the map of what to know. The platform side (Cloudflare in front, CI/CD, Kubernetes) is in Conrad DevOps.

Know

PageCoversQuestions
Request path and cachingFrom URL to hydration, stale-while-revalidate, getting a price change through every layer, consent and A/B variants on cached pages, how you cached at Develit5
HTTP cachingCache-Control directives, freshness and validation with ETag and Last-Modified, weak tags, 304, private versus shared caches, proxies7
Cloudflare's cacheWhat Cloudflare caches by default, CF-Cache-Status, Cache Rules, edge versus origin for HTML, why a short shared cache is hard on Workers4
Nitro's cacheCached handlers and route rules, every option, the key layout, where entries live, sharing them through Redis, purging, what the browser should be told7
  • Drill them: Train, press Only next to Conrad caching, Smart order. Or open the note and press Practise … from this note.
  • Rehearse: run a mock interview with Conrad caching and Conrad DevOps selected.

Be able to say

Be able to say· How should a large e-shop cache, in one minute?

"Three layers. The browser keeps the hashed JavaScript, CSS and images for a year, because a change means a new file name, and it always revalidates the HTML with an ETag, so a deploy shows up on the next visit. The CDN sits in front as a reverse proxy: it caches those same static files and product images close to users, and adds the WAF and bot protection. The server is where the HTML is rendered, and that's where the rendered pages are cached, in Redis for about a minute with stale-while-revalidate, because the HTML has too many variants, by device, language, country and customer type, to live in a CDN. API responses are cached on the server for minutes to hours depending on the data, and never when they're personal."

Pages in this section

  1. 01Request path and cachingHow a request reaches a Conrad storefront page and becomes interactive, and the cache layers along the way — browser, Cloudflare CDN, Valkey with stale-while-revalidate, Apigee and Nitro's cache — with the headers that control them and what happens to cached HTML during deploys.
  2. 02HTTP cachingCache-Control directives, freshness and validation with ETag and Last-Modified, 304 responses, private versus shared caches, and what a reverse proxy is — the HTTP caching part of your Conrad Caching note.
  3. 03Cloudflare's cacheWhat Cloudflare caches by default and what it passes through as DYNAMIC, the CF-Cache-Status values, Cache Rules and edge TTLs, purging, and why HTML belongs at the origin when it has many variants.
  4. 04Nitro's cachedefineCachedEventHandler, cachedFunction and route-rule cache — every option, what swr does on the server and in the header, where entries live, sharing them through Redis or Valkey, and the headers the browser should get for cached HTML.

Your notes

Open in Notes

Nothing yet. Notes filed here show up on every page of this section.

Nuxt under the hood

Questions and flashcards from your Nuxt internals note — carrying values from build time to runtime, the start-up sequence from config loading to the bundles, module order and modules:done, config priority across layers, Nitro and h3, why h3 instead of Express, how a request reaches the Vue renderer, and deployment presets.

Request path and caching

How a request reaches a Conrad storefront page and becomes interactive, and the cache layers along the way — browser, Cloudflare CDN, Valkey with stale-while-revalidate, Apigee and Nitro's cache — with the headers that control them and what happens to cached HTML during deploys.