Write-Through vs Write-Back Cache - Which Should You Use? (System Design #6)
Caching makes systems fast - but it also introduces one of the hardest problems in computer science: keeping your cache and database in sync.
Caching makes systems fast - but it also introduces one of the hardest problems in computer science: keeping your cache and database in sync.
What’s in the video (6m 36s)
- 0:00 — Introduction to Cache Write Strategies & Cache Invalidation
- 0:31 — What is Latency?
- 0:48 — What is Cache?
- 1:26 — How to Keep Cache in Sync with the Database?
- 1:58 — What is Write-Through Cache?
- 2:27 — How a Write-Through Cache Works? and its Tradeoffs
- 3:00 — Write-Around and Write-Back Cache
- 3:12 — What is Write-Around Cache?
- 3:32 — What is Write-Back Cache?
- 3:50 — Write-Through vs Write-Around vs Write-Back Cache
- 4:31 — What is Cache Invalidation?
- 5:32 — Cache Write Strategies & Cache Invalidation Tradeoffs
Resources
- Full System Design series: YouTube playlist
- Previous episode: https://youtu.be/_ZYBCFxL-MI
- Next episode: https://youtu.be/r5hKRooGDuQ
For more in this series, visit the #system-design tag page or jump to the channel uploads list for everything else.
Related posts
How to Crack Any System Design Interview — Full Beginner's Guide
Most candidates fail system design interviews not because they lack knowledge — but because they don't have a clear framework to structure their thinking.
Design a Scalable System from Scratch — Full Blueprint (System Design #15)
You've learned the pieces. Now let's put them all together and design a real scalable system from scratch — the way it's done in interviews and in production.
Monolith vs Microservices - Which Architecture Should You Choose? (System
Microservices are everywhere - but are they always the right choice? Spoiler: most teams adopt them too early, and it costs them.