Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Architecture
Architecturemedium

Cache-aside vs write-through — what’s the difference?

Tags
#cache#cache-aside#write-through#consistency
Back to categoryPractice quiz

Answer

Cache-aside: app reads from cache, on miss loads from DB and populates cache; writes go to DB and cache is updated/invalidated. Write-through: writes go through the cache which also writes to DB, keeping cache in sync but adding write latency.

Related questions

Architecture
What is eventual consistency and how do you explain it to a user?
#consistency#distributed-systems#eventual-consistency
Architecture
What is Event-Driven Architecture (EDA)?
#event-driven#architecture#messaging
Architecture
What is the CAP Theorem?
#distributed-systems
#theory
#consistency
MongoDB
Read preference in replica sets: what does `primary` vs `secondary` mean?
#mongo#replica-set#read-preference
MongoDB
Read concern vs write concern: what do they control?
#mongo#consistency#read-concern
Databases
Autocommit vs explicit transactions: when does it matter?
#database#transactions#autocommit