NOTE

2.3 Distributed Transaction Solution: Reliable-Message Eventual Consistency

1. What Is Reliable-Message Eventual Consistency - A distributed transaction solution that guarantees eventual consistency. 2. Reliable-Message Eventual-Consistency Process. 3. Use Cases - Suitable for businesses that require eventual consistency, have low time sensitivity, and where the distributed transaction can only succeed rather than fail, such as awarding points after registration or coupons after login.

Distributed SystemsCreated Updated 1 min readhistorical

This is a historical learning note and may contain outdated or incomplete understanding.

1. What Is Reliable-Message Eventual Consistency?

A distributed transaction solution that guarantees eventual consistency.

2. Reliable-Message Eventual-Consistency Process

Local Message Table - Reliable-Message Eventual Consistency

3. Use Cases for Reliable-Message Eventual Consistency

  • Suitable for businesses that require eventual consistency, have low time sensitivity, and where the distributed transaction can only succeed rather than fail, such as awarding points after registration or coupons after login.
  • Multiple services use multiple data sources, and the data sources do not have to be DBs.

4. Implementations of Reliable-Message Eventual Consistency

4.1. Local Message Table

Local Message Table - Local Message Table

4.2. Transaction Messages

Compared with a local message table, this is equivalent to moving the background scheduled task + message table into the message-queue middleware for implementation.

Local Message Table - Transaction Messages

5. References

Discussion

Sign in with GitHub to comment. Discussions are stored as GitHub Issues.View on GitHub