NOTE

2.4 Distributed Transaction Solution: Best-Effort Notification

1. What Is Best-Effort Notification - A distributed transaction solution that guarantees eventual consistency. 2. Best-Effort Notification Process. 3. Use Cases - Suitable for businesses that require eventual consistency, have low time sensitivity, allow a small number of distributed transactions to fail, and where the passive side's processing result does not affect the active side's processing result, such as bank notifications and payment-result notifications.

Distributed SystemsCreated 06/01/2021Updated 03/08/20221 min readhistorical

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

1. What Is Best-Effort Notification?

A distributed transaction solution that guarantees eventual consistency.

2. Best-Effort Notification Process

Best-Effort Notification - External System

3. Use Cases for Best-Effort Notification

Suitable for businesses that require eventual consistency, have low time sensitivity, allow a small number of distributed transactions to fail, and where the passive side’s processing result does not affect the active side’s processing result, such as bank notifications and payment-result notifications.
Multiple services use multiple data sources, and the data sources do not have to be DBs.

4. Best-Effort Notification Implementations

5. References

Discussion

JavaScript is required to load comments.Open the discussion on GitHub