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/Microservices
Microserviceshard

What is the Outbox pattern and what problem does it solve?

Tags
#outbox#events#consistency#reliability
Back to categoryPractice quiz

Answer

It writes an event/message to an “outbox” table in the same DB transaction as the business change, then publishes it asynchronously. This avoids losing events when the DB commit succeeds but publishing fails.

Related questions

Microservices
Kafka ordering: what ordering guarantees do you get and how do you design for ordering?
#microservices#kafka#ordering
Microservices
Why is synchronous fan-out (one request calling many services) risky, and how do you reduce it?
#microservices#fan-out#latency
Microservices
In a saga, what is a compensating action and why is it tricky?
#microservices#saga#compensation
Microservices
Saga orchestration vs choreography — what’s the difference?
#saga#orchestration#choreography
Microservices
If services can’t share a DB, how do they share data?
#contracts#events#api
Microservices
Distributed locks — when do you need them and what are the risks?
#distributed-lock#coordination#reliability