Skip to content

Home

Jump to bottom
sharajava edited this page Jan 9, 2019 · 32 revisions

FESCAR: Fast & EaSy Commit And Rollback

License

What is FESCAR?

A distributed transaction solution with high performance and ease of use for microservices architecture.

Distributed Transaction Problem in Microservices

Let's image a traditional monolithic application. Its business is built up with 3 modules. They use a single local data source.

Naturally, data consistency will be guaranteed by local transaction.

Monolithic App

Thing changed in microservices architecture. The 3 modules mentioned are designed to be 3 services on top of 3 different data sources (Pattern: Database per service). Data consistency within every single service is naturally guaranteed by local transaction.

But how about the whole business logic scope?

Microservices Problem

How FESCAR do?

FESCAR is just a solution for problem mentioned above.

FESCAR solution

Firstly, how to define a Distributed Transaction?

We say, a Distributed Transaction is a Global Transaction which is made up with batch of Branch Transation, and normally Branch Transation is just Local Transaction.

Global & Branch

There are 3 basic components in FESACR:

  • **Transaction Coordinator(TC): **Maintain status of global and branch transactions, drive the global commit or rollback.
  • **Transaction Manager(TM): **Define the scope of global transaction: begin a global transaction, commit or rollback a global transaction.
  • **Resource Manager(RM): **Manage resources that branch transactions working on, talk to TC for registering branch transactions and reporting status of branch transactions, and drive the branch transaction commit or rollback.

Model

A typical lifecycle of FESCAR managed distributed transaction:

  1. TM asks TC to begin a new global transaction. TC generates a XID representing the global transaction.
  2. XID is propagated through microservices' invoke chain.
  3. RM register local transaction as a branch of the corresponding global transaction of XID to TC.
  4. TM asks TC for committing or rollbacking the corresponding global transaction of XID.
  5. TC drives all branch transactions under the corresponding global transaction of XID to finish branch committing or rollbaking.

Typical Process

For more details about principle and design, please go to FESCAR wiki page.

History

  • TXC: Taobao Transaction Constructor. Alibaba middleware team start this project since 2014 to meet dirstribuited transaction problem caused by application architecture change from monolithic to microservices.
  • GTS: Global Transaction Service. TXC as a Aliyun middleware product with new name GTS was published since 2016.
  • FESCAR: we start the open source project FESCAR based on TXC/GTS since 2019 to work closly with community in the future.

Quick Start

Quick Start

Clone this wiki locally