Skip to content
_CORE
AI & Agentic Systems Core Information Systems Cloud & Platform Engineering Data Platform & Integration Security & Compliance QA, Testing & Observability IoT, Automation & Robotics Mobile & Digital Banking & Finance Insurance Public Administration Defense & Security Healthcare Energy & Utilities Telco & Media Manufacturing Logistics & E-commerce Retail & Loyalty
References Technologies Blog Know-how Tools
About Collaboration Careers
CS EN DE
Let's talk

Distributed Transactions — Overview

23. 07. 2025 1 min read intermediate

Architecture Expert

Distributed Transactions — Overview

Distributed TransactionsOutbox2PC 3 min read

How to handle transactions across microservices. 2PC, Saga, Outbox pattern, and TCC.

2PC

Two-Phase Commit: blocking, slow, coordinator = SPOF. Not used in microservices.

Outbox Pattern

BEGIN;
INSERT INTO orders (id, total) VALUES ('ord-1', 1000);
INSERT INTO outbox (aggregate_type, payload) VALUES (
    'Order', '{"type": "OrderCreated", "orderId": "ord-1"}'
);
COMMIT;
-- Debezium CDC reads the outbox and publishes events

Saga vs TCC

  • Saga — sequence of local transactions + compensation
  • TCC (Try-Confirm-Cancel) — reservation, then confirmation/cancellation

Summary

Saga is the most common choice, Outbox solves reliable messaging. Avoid 2PC in microservices.

Need Help with Implementation?

Our team has experience designing and implementing modern architectures. We’re happy to help.

Free Consultation

Share:

CORE SYSTEMS team

We build core systems and AI agents that keep operations running. 15 years of experience with enterprise IT.