Shulou(Shulou.com)06/01 Report--

This article mainly introduces the relevant knowledge of "what is the life cycle of FESCAR managing distributed transactions". The editor shows you the operation process through an actual case. The operation method is simple, fast and practical. I hope this article "what is the life cycle of FESCAR management distributed transactions" can help you solve the problem.

What is FESCAR?

A distributed transaction solution with a micro-service architecture with high performance and ease of use.

Distributed transaction problems in Micro Services

Let's imagine a traditional monolithic application. Its business consists of three modules. They use a single local data source.

Of course, local transactions can ensure data consistency.

The microservice architecture has changed. The three modules mentioned are designed as three services on top of three different data sources (schema: the database of each service). Local transactions naturally ensure data consistency in each service.

But what about the overall scope of business logic?

What does FESCAR do?

FESCAR is just the solution to the above problems.

First, how do you define distributed transactions?

We say that a distributed transaction is a global transaction, consisting of a batch of Branch Transation, and usually the Branch Transation is just a local transaction.

FESACR has three basic components:

Transaction coordinator (TC): maintains the state of global and branch transactions and drives global commit or rollback.

Transaction Manager (TM): define the scope of the global transaction: start the global transaction, commit or roll back the global transaction.

Resource Manager (RM): manages resources for branch transactions, communicates with TC to register branch transactions, reports the status of branch transactions, and drives branch transactions to commit or rollback.

FESCAR manages the typical lifecycle of distributed transactions:

TM asked TC to start a new global deal. TC generates a XID that represents a global transaction.

XID propagates through the call chain of microservices.

RM registers the local transaction as a branch of the corresponding global transaction from XID to TC.

TM requires TC to commit or roll back the corresponding global transaction for XID.

TC drives all branch transactions under the corresponding global transaction of XID to complete branch commit or rollbaking.

For more details on the principle and design, visit the FESCAR wiki page.

History

TXC: Taobao transaction constructor. The Alibaba middleware team has launched the project since 2014 to meet the direct transaction problems caused by the transformation of the application architecture from a single service to a micro service.

GTS: global trading service. TXC as an Aliyun middleware product, the new name GTS has been released since 2016.

FESCAR: we have been based on the TXC / GTS open source project FESCAR since 2019 to work closely with the community.

That's all for "what is the life cycle of FESCAR managing distributed transactions". Thank you for reading. If you want to know more about the industry, you can follow the industry information channel. The editor will update different knowledge points for you every day.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.