Architectural Caching Patterns for Kubernetes
summary
Compares concrete caching topologies on Kubernetes and shows which one to pick by claim and evidence: demoed architectures include Sidecar Caching, Reverse Proxy Caching with Nginx, and Envoy-level caching with Service Mesh; Hazelcast appears as a reverse-proxy sidecar option. Each pattern includes sample configuration, operational trade-offs (latency, consistency, deployment complexity), and failure modes so the decision is driven by measurable costs and what actually gets built and operated rather than vague promises.
AI-written summary · about
chapters (9)
- 0:00Kubernetes caching patterns
- 2:35Why caching matters
- 5:56Distributed caching topologies
- 9:08Client-server vs cloud-native caching
- 12:47Language-agnostic caching solutions
- 17:06Reverse proxy caching
- 20:22Service versioning and caching
- 22:52Reverse proxy best practices
- 24:19On-premises vs cloud caching
related talks
43mWhere Is My Cache? Architectural Patterns for Caching ...
34mAdvanced Caching Patterns used by 2000 microservices
46mA Hitchhiker’s Guide to Caching Patterns
43mCache Me Outside - Caching Methodologies & Architectures
15mBuilding Self-Healing Cache Infrastructure
30mCaching patterns for lazy devs for lazy loading
44mCatch Me If You Cache: Cache Patterns and Pitfalls in Production
27mCaching for Cash
