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
Microservicesmedium

In a saga, what is a compensating action and why is it tricky?

Tags
#microservices#saga#compensation#consistency
Back to categoryPractice quiz

Answer

A compensating action is a business operation that “undoes” a previous step (e.g., cancel a reservation after payment fails). It’s tricky because it’s not a real rollback: it can fail, it may not perfectly restore the previous state, and it must be idempotent and well-observed.

Related questions

Microservices
Trace context propagation: what is the `traceparent` header and why should services forward it?
#microservices#observability#tracing
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
REST vs gRPC for service-to-service calls: what are the key trade-offs?
#microservices#grpc#rest
Microservices
BFF (Backend for Frontend): what is it and when does it help?
#microservices#bff#api
Microservices
Multi-region microservices: what are the main benefits and the main pain points?
#microservices#multi-region#availability