Caching
There are only two hard things in computer science: cache invalidation and naming things. These posts cover both halves of the first one: HTTP cache headers, Redis, CDN behavior, thundering herds, and what to do when the cache is the problem instead of the solution.
Redis Is a Database You Forgot to Capacity-Plan
Redis holds state in finite RAM, so it is a database with a capacity plan, not a magic speed layer. Unbounded keys, eviction policies, and the OOM cliff.
Read more BackendREST vs GraphQL Is Over. You're Now Running Both, Badly.
REST vs GraphQL got declared a tie: use both. Nobody costs that out. Two contracts, the HTTP caching you lost, a leaky BFF, and the N+1 that just moved.
Read more BackendThe Cache-Control Header You're Probably Ignoring
Most developers set max-age and call it done. The directives that matter for CDN behavior, revalidation, and stale content are all sitting there unused.
Read more BackendWhy Your Service Slows Down at 9am Every Day
Your service slows every morning for the same five reasons: JVM warmup, cold caches, pool growth, clustered crons, deployment timing. Here's how to fix each.
Read more BackendThe Thundering Herd Problem
Cache stampedes, retry storms, reconnect floods: three failure modes with the same root cause. Synchronized behavior under load amplifies failures every time.
Read more BackendCaching Is Easy Until It Isn't
Redis, in-memory, CDN: caching feels simple until invalidation ruins your week. Here's how each caching layer bites you and what I learned the hard way.
Read more