Advanced Caching Patterns used by 2000 microservices
summary
Wix handles >500 billion HTTP requests and >1.5 billion Kafka events per day and documents three concrete patterns: Configuration Data Cache persists startup-critical config to local disk or S3 so services boot with stale-but-available data; DynamoDB+CDC based Cache keeps an in-memory LRU per instance repopulated from DynamoDB events via Kafka (Greyhound) for near-zero read latency and fast warmup; HTTP Reverse Proxy Caching uses Varnish with ETag purge events to serve hot HTML at the edge.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 1:19Why caching matters at Wix
- 4:48When to use caching patterns
- 9:02Static config cache with Koboshi
- 12:51DynamoDB in-memory cache pattern
- 22:41HTTP reverse proxy cache with Varnish
- 29:48Choosing the right cache pattern
- 32:00Resources and closing remarks
- 33:02Q&A session
related talks
41mBattle-tested event-driven patterns for your microservices
47mArchitectural Patterns for Caching Microservices
43mBattle-tested event-driven patterns for your Microservices archit.
45mWhere is my cache? Architectural patterns for caching microservices by example
43mWhere Is My Cache? Architectural Patterns for Caching ...
25mArchitectural Caching Patterns for Kubernetes
54mLessons learned from working with 2000 event-driven microservices
46mLessons Learned From Working with 2000 Event-Driven Microservices
