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
Architecturehard

Event sourcing: what is it and what are the main trade-offs?

Tags
#architecture#event-sourcing#events#trade-offs
Back to categoryPractice quiz

Answer

Event sourcing stores state as a sequence of events (facts), and current state is rebuilt by replaying them into a projection. Benefits: audit trail, easy history, and time-travel/debugging. Trade-offs: higher complexity, event schema evolution, more moving parts (projections), and harder ad-hoc queries.

Related questions

Architecture
Anti-corruption layer (ACL): what is it and when would you use it?
#architecture#ddd#integration
Architecture
What is an ADR (Architecture Decision Record) and why is it useful?
#architecture#documentation#decisions
Architecture
What is a reverse proxy and what is it commonly used for?
#architecture#reverse-proxy#http
Architecture
CORS: what is it and what does it NOT protect you from?
#architecture#web#cors
Architecture
Graceful degradation: what does it mean and how do you design for it?
#architecture#resilience#fallbacks
Architecture
Cache stampede (thundering herd): what is it and how do you mitigate it?
#architecture#caching#cache-stampede