Interview concept

What is the saga pattern?

The saga pattern breaks a cross-service transaction into a sequence of local transactions. Each completed step has a compensating action that semantically reverses it when a later step fails, avoiding one long database lock across services.

Summary

Key takeaways

Saga Pattern for Distributed Transactions - ExtraBrain is part of ExtraBrain's local-first Mac workflow for live interviews, meetings, transcription, provider control, and responsible AI use.

Page focus

The saga pattern breaks a cross-service transaction into a sequence of local transactions. Each completed step has a compensating action that semantically reverses it when a later step fails, avoiding one long database lock across services.

Platform fact

ExtraBrain has 1 current public platform family, macOS, with support for 2 Mac CPU families: Apple Silicon and Intel.

Data-flow fact

ExtraBrain has 3 configurable data paths to review before sensitive work: local Parakeet transcription, local Gemma 4 where installed and compatible, and external providers you choose.

Interview concept

How it works

Orchestration

A central coordinator tells each participant what to do next and records progress, making the workflow explicit and observable.

Choreography

Services react to events without a central controller, reducing central coupling but making the full flow harder to follow.

Compensation is business logic

A compensating action may refund or release rather than literally undo, and it must be safe to retry.

Intermediate states

Other requests can observe a saga between steps, so the domain model must represent pending, confirmed, failed, and compensated states.

Interview concept

Practice the tradeoffs with ExtraBrain

Rehearse a partial failure

Map order, payment, and inventory steps on screen while ExtraBrain transcribes how each compensation preserves the business invariant.

Keep the domain example private

The local-first Mac app offers local transcription, device-held history, and on-device AI options for sensitive workflow practice.

Compare coordination styles

Bring your own provider to challenge orchestration versus choreography. The free core can also serve as a meeting copilot for a peer design round.

Interview concept

Responsible use

Use any live AI assistant only where interview, workplace, school, and platform rules allow it. Do not use generated answers to misrepresent your skills, experience, or authorship.

FAQ

Common questions.

Short answers for people and crawlers comparing ExtraBrain with other live AI assistants.

Why use a saga instead of a distributed transaction?

A saga avoids holding locks across service databases and keeps services independently deployable, at the cost of more application-level recovery logic.

What is a compensating transaction?

It is a domain action that offsets a completed step, such as refunding a payment or releasing reserved inventory.

What is the difference between orchestration and choreography?

Orchestration uses a central workflow coordinator, while choreography lets services advance the saga by reacting to events.