Caching the uncacheable in Varnish
summary
Shows how Varnish extends default behavior to cache personalized pages: extract and hash language or session cookie values, parse ESI fragments at the edge, verify JWTs and do basic auth in VCL, and fetch session data from Redis to synthesize JSON responses so origins see far fewer hits. Claims a single machine can reach 1.3 terabits per second and the official Docker image has ~10 million Docker pulls. Demonstrates modules for cookie, digest, Redis, an Edge mustache parser, and an experimental Project Sledgehammer (WASM) runtime.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:03Why caching essential
- 10:21How Varnish works
- 16:36HTTP headers complexities
- 24:58Handling cookies
- 31:36Edge Side Includes
- 35:28Edge computations with VCL
- 43:22Synthetic responses
- 47:37Personalized edge data
- 51:08Deploying Varnish
- 54:18Future: WebAssembly in Varnish
related talks
58mCaching the uncacheable: delivering personalized experiences without sacrificing performance
28mCaching the uncacheable in Varnish
38mHTTP Headers that Make Your Website Go Faster
38mThe power of cache in a slow world
28mTaking Laravel to the edge with HTTP caching & Varnish
25mCaching strategies on https://dev.to
46mVarnish for PHP developers
37mVarnish tips & tricks