Cache me if you can: Boosted application performance with Redis and client-side caching
summary
A concrete recipe for client-side caching with Redis: use redis-py 5.1.1+ with RESP3 + Redis 7.4+, enable the client cache (LRU by item count, default key = command+keys), and rely on client tracking push invalidations so server-side writes invalidate local copies. Demo uses 10,000 sequential keys, 1,000-item local cache (10%), poor network, showing uncached ~600 reads/s and 300 writes whereas client caching halves remote reads and shifts load locally. Synchronous API only today; async support and semantic/vector caching services are coming.
AI-written summary · about
chapters (11)
- 0:00Introduction to the speaker
- 1:22Overview of Redis use cases
- 4:03Caching basics and patterns
- 6:48Managing cache accuracy
- 8:43Benefits of client-side caching
- 10:51Live demo of client-side caching
- 15:08Implementing client tracking
- 16:54Client library architecture
- 21:25Getting started with code
- 22:54Ecosystem updates and features
- 26:50Q&A session
related talks
17mCache me if you can: Boosting performance with Data Caching in Python
50mMake API Calls Wicked Fast with Redis
42mCaching for Cash
36mCache is King
49mCache à la carte: a framework for in-memory caching
36mCaching Strategies for an Erlang Based Web Stack
30mCaching patterns for lazy devs for lazy loading
51mX-Raying Your Redis App: SDK Tuning with a Performance Engineer’s Eye