Skip to main content

Explain the Saga pattern.

Entry Microservices
Quick Answer Saga pattern handles distributed transactions across multiple services without a single ACID transaction. Each service does its local transaction and publishes an event. If a later step fails, compensating transactions roll back previous steps. Two styles: choreography (services react to events) and orchestration (a saga coordinator drives the steps).

Answer

Sagas coordinate distributed transactions by using a sequence of local transactions. If one step fails, compensating actions revert previous changes.

S
SugharaIQ Editorial Team Verified Answer

This answer has been peer-reviewed by industry experts holding senior engineering roles to ensure technical accuracy and relevance for modern interview standards.

Want to bookmark, take notes, or join discussions?

Sign in to access all features and personalize your learning experience.

Sign In Create Account

Source: SugharaIQ

Ready to level up? Start Practice