A Change-Data-Capture use-case: designing an evergreen cache
summary
Claim: use CDC to keep a cache evergreen by streaming DB changes into the cache. Implementation reads the MySQL binlog via bezium, runs a small pipeline on hazelcast jet and updates two in-memory maps (query cache + entity cache) used by a Spring Boot app. Demo shows external updates (a batch or separate app) are caught and the cache refreshes near real time, avoiding fragile triggers or naive TTLs and working without mandatory Kafka.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:56Why caching matters
- 4:23Cache invalidation vs eviction
- 9:02Event-driven cache updates
- 13:16Change data capture basics
- 17:33Debezium for CDC
- 20:02Hazelcast for streaming
- 23:36Integrating components
- 24:20Demo setup
- 27:56Live cache update demo
- 30:44Summary and resources
related talks
32mA Change-Data-Capture use-case: designing an evergreen cache
41mA Change-Data-Capture use-case: designing an evergreen cache
01mA Change-Data-Capture use-case: designing an evergreen cache
35mChange Data Capture: The Magic Wand We Forgot #bbuzz
28mCache for Cash—Speeding Up Production with Kafka and MySQL binlog
01h 09mOpen-source Change Data Capture With Debezium
22mChange Data Capture: Exploring YugabyteDB’s Modern Design
36mEvent-Driven Change Data Capture pattern