Search Results for "saga"

...Easy for go, python, php, nodejs, ruby and so forth. The only external dependence is the database server, easy to deploy, cluster, and scale horizontally. Supports TCC, SAGA, XA, and transaction messages. DTM is a distributed transaction framework that provides cross-service eventual data consistency. It provides saga, tcc, xa, 2-phase message, and outbox patterns for a variety of application scenarios. It also supports multiple languages and multiple store engines to form up a transaction.

...Its architecture separates responsibilities into a global coordinator and per-service participants, so business services remain decoupled while transactions are orchestrated centrally. Multiple modes are supported—AT (automatic, SQL-based with undo logs), TCC (try-confirm-cancel), Saga (long-running compensation), and XA—letting architects choose between simplicity, control, and interoperability. The AT mode is notable for minimizing code changes: Seata captures before/after images of SQL updates and can roll back on failure to maintain atomicity across services. Integrations cover common RPC frameworks and registries, enabling drop-in usage within Spring Cloud/Dubbo-style ecosystems.

Seata, or Simple Extensible Autonomous Transaction Architecture is an open source distributed transaction solution that brings high performance and easy-to-use distributed transaction services under a microservices architecture. It has 3 basic components: a Transaction Coordinator for maintaining the status of global and branch transactions; a Transaction Manager that defines the scope of global transaction; and a Resource Manager that manages resources being worked on by branch...