Cache all the things for fast and simple backends
summary
Claims a system that makes serving only cached HTTP requests possible for dynamic data by putting a custom reverse proxy in front of the app which funnels all GETs from cache and sends all writes through to the origin. Upstream API has a hard rate limit of four requests per second, so the proxy implements automatic cache warming and updates content rather than invalidate using standard HTTP headers, replacing a Redis mirroring approach and keeping responses fresh while reducing origin traffic.
AI-written summary · about
chapters (3)
related talks
25mCaching strategies on https://dev.to
47mCaching strategies on https://dev.to
34mAdvanced Caching Patterns used by 2000 microservices
30mCaching, Payloads, and Other Dark Arts
56mCaching the uncacheable in Varnish
30mAsk Your Proxy, It Knows Everything
45mWhere is my cache? Architectural patterns for caching microservices by example
35mCaching at Netflix: The Hidden Microservice