BestHub
Sign in
Tagged articles

eventual consistency

61 articles · Page 1 of 1
Ray's Galactic Tech
Ray's Galactic Tech
Aug 14, 2026 · Backend Development

Payment Callback After Order Cancellation? 3 Consistency Challenges and Practical Engineering Solutions

The article examines why payment callbacks that arrive later than order cancellations cause money‑in‑order‑canceled anomalies, outlines the three core eventual‑consistency problems—message ordering, duplicate consumption, and message loss—and presents a complete engineering solution using business idempotency keys, a transactional outbox, state‑machine handling, and reconciliation compensation.

IdempotencyKafkaReconciliation
0 likes · 35 min read
Payment Callback After Order Cancellation? 3 Consistency Challenges and Practical Engineering Solutions
Code Farming
Code Farming
Jun 19, 2026 · Backend Development

Nail Distributed Transaction Consistency Questions in Interviews with This Full‑Score Answer

The article explains why reciting the 2PC protocol fails in real‑world interviews, then walks through the two dominant solutions—two‑phase commit and MQ‑based eventual consistency—detailing their mechanisms, trade‑offs, and a concrete interview response template that showcases practical experience and theoretical depth.

Interview PreparationMessage QueueMicroservices
0 likes · 6 min read
Nail Distributed Transaction Consistency Questions in Interviews with This Full‑Score Answer
ZhiKe AI
ZhiKe AI
Jun 14, 2026 · Fundamentals

Why Consistency Is a Luxury: A Practical Guide to BASE Theory in Distributed Systems

During peak events like Alibaba's Double‑11 and WeChat's red‑packet frenzy, distributed systems must trade strict consistency for availability; this article explains the CAP theorem, introduces the BASE model, compares CP and AP designs, and provides real‑world case studies and selection guidelines.

ACIDBASE theoryCAP theorem
0 likes · 15 min read
Why Consistency Is a Luxury: A Practical Guide to BASE Theory in Distributed Systems
ZhiKe AI
ZhiKe AI
Jun 13, 2026 · Fundamentals

Why Banks Let You Wait but Never Miscalculate: A 5‑Minute Guide to the CAP Theorem

Every delay you notice in WeChat messages, flash‑sale pages, or bank transfers stems from the same underlying distributed‑system trade‑off, and this article explains the CAP theorem, its three guarantees, common misconceptions, and how CP versus AP architectures shape real‑world services.

BASE modelCAP theoremCP vs AP
0 likes · 11 min read
Why Banks Let You Wait but Never Miscalculate: A 5‑Minute Guide to the CAP Theorem
IT Services Circle
IT Services Circle
May 15, 2026 · Backend Development

When Splitting a System into 200 Microservices Almost Ruined the Company

The article uses a night‑market analogy to explain practical microservice design, covering domain‑based service decomposition, service discovery, communication protocols, data consistency strategies, fault‑tolerance, rate limiting, and monitoring, while warning against over‑splitting and unnecessary complexity.

MicroservicesMonitoringcircuit breaker
0 likes · 14 min read
When Splitting a System into 200 Microservices Almost Ruined the Company
Xiaokun's Architecture Exploration Notes
Xiaokun's Architecture Exploration Notes
Jul 20, 2025 · Databases

How to Achieve Linear Consistency in Single-Leader Replication: Challenges and Solutions

This article examines eventual and linear consistency in leader‑based replication, explains read‑your‑writes and shared‑data scenarios, discusses replication lag, failover trade‑offs, multi‑data‑center risks, and shows how consensus systems like ZooKeeper and etcd implement true linear consistency.

Databasesdistributed systemseventual consistency
0 likes · 13 min read
How to Achieve Linear Consistency in Single-Leader Replication: Challenges and Solutions
IT Architects Alliance
IT Architects Alliance
Jan 13, 2025 · Fundamentals

Strong Consistency vs. Eventual Consistency in Distributed Systems

The article explains the principles, implementation techniques, trade‑offs, and typical use cases of strong consistency and eventual consistency in distributed systems, helping architects decide which model best fits the performance, availability, and correctness requirements of their applications.

CAP theoremconsistencyeventual consistency
0 likes · 13 min read
Strong Consistency vs. Eventual Consistency in Distributed Systems
JavaEdge
JavaEdge
Nov 16, 2024 · Backend Development

How Netflix Built a Low‑Latency Distributed Counter Service at Scale

This article explains Netflix's distributed counter abstraction built on their time‑series service, detailing use cases, API design, counter types, implementation methods, control‑plane configuration, performance results, and future work to achieve near‑real‑time, low‑latency counting at massive scale.

Backend ArchitectureNetflixcounter service
0 likes · 25 min read
How Netflix Built a Low‑Latency Distributed Counter Service at Scale
Sanyou's Java Diary
Sanyou's Java Diary
Jun 17, 2024 · Backend Development

How to Keep Cache and Database Consistent? Proven Strategies and Common Pitfalls

This article explains why cache‑DB consistency is a long‑standing challenge, compares naive full‑load and delete‑cache approaches, analyzes concurrency and failure scenarios, and presents reliable solutions such as updating the database first followed by cache deletion using message queues or binlog subscriptions.

Cache ConsistencyDatabase SynchronizationRedis
0 likes · 19 min read
How to Keep Cache and Database Consistent? Proven Strategies and Common Pitfalls
Code Ape Tech Column
Code Ape Tech Column
Jun 6, 2023 · Backend Development

Business Compensation Mechanisms: Rollback and Retry Strategies in Distributed Systems

The article explains business compensation mechanisms in distributed microservice architectures, detailing rollback and retry approaches, their implementation patterns, strategies, and practical considerations for achieving eventual consistency while handling failures and outlines best practices for idempotency, monitoring, and workflow engine design.

Rollbackbusiness compensationdistributed systems
0 likes · 14 min read
Business Compensation Mechanisms: Rollback and Retry Strategies in Distributed Systems
Architects Research Society
Architects Research Society
May 21, 2023 · Fundamentals

Immutable Architecture, CAP Theorem, and CRDTs – Insights from Michael Perry

Michael Perry discusses his book on immutable architecture, exploring the eight myths of distributed computing, the impact of Pat Helland’s “immutability changes everything”, CAP theorem, eventual consistency, location‑independent identities, and CRDTs, while offering practical advice for applying these concepts in real‑world enterprise systems.

CAP theoremCRDTeventual consistency
0 likes · 27 min read
Immutable Architecture, CAP Theorem, and CRDTs – Insights from Michael Perry
Architects Research Society
Architects Research Society
Apr 21, 2023 · Databases

Understanding Sequential, Causal, and Eventual Consistency Models

This article explains the concepts of sequential, causal, and eventual consistency in distributed systems, illustrating their guarantees with examples and diagrams, and discusses related consistency guarantees such as monotonic reads, writes, and read‑your‑writes, helping readers grasp how these models affect system behavior and performance.

causal consistencyconsistencyeventual consistency
0 likes · 13 min read
Understanding Sequential, Causal, and Eventual Consistency Models
Baidu Geek Talk
Baidu Geek Talk
Apr 17, 2023 · Operations

Baidu DuoLiXiong Platform Stability Construction: Practices and Insights

Baidu's DuoLiXiong platform, a SaaS suite for local services, achieves stability through comprehensive technical and business specifications, microservice best practices, rigorous code reviews, automated monitoring, eventual consistency, idempotency, and future automated scaling and intelligent fault tolerance for critical operations.

Code ReviewDevOpsIdempotency
0 likes · 11 min read
Baidu DuoLiXiong Platform Stability Construction: Practices and Insights
ITPUB
ITPUB
Feb 13, 2023 · Fundamentals

How a Bat-Borne Virus Explains the Gossip Protocol in Distributed Systems

Using a fictional coronavirus carried by a bat, the article illustrates the Gossip protocol’s mechanisms—direct mail, anti-entropy, and epidemic spread—to explain how distributed systems achieve eventual consistency, highlighting advantages, drawbacks, and practical considerations for storage components like Cassandra.

Anti-entropyData Replicationdistributed systems
0 likes · 10 min read
How a Bat-Borne Virus Explains the Gossip Protocol in Distributed Systems
Top Architect
Top Architect
Sep 23, 2022 · Backend Development

Event‑Driven Architecture and Ensuring Eventual Consistency in Microservices

The article explores event‑driven architecture in microservices, detailing transaction consistency challenges, eventual consistency solutions, domain‑driven design, bounded contexts, and practical patterns such as local transaction tables, event sourcing, and materialized views to achieve reliable distributed systems.

DDDevent-driveneventual consistency
0 likes · 15 min read
Event‑Driven Architecture and Ensuring Eventual Consistency in Microservices
Top Architect
Top Architect
Sep 15, 2022 · Backend Development

Event‑Driven Architecture and Distributed Transaction Consistency in Microservices

The article explains how traditional ACID transaction guarantees break down in microservice environments, discusses the challenges of distributed transactions, and presents event‑driven architectures, eventual consistency, domain services, materialized views, and practical patterns such as local transaction tables and event sourcing to achieve reliable consistency across services.

DDDarchitectureevent-driven
0 likes · 15 min read
Event‑Driven Architecture and Distributed Transaction Consistency in Microservices
MaGe Linux Operations
MaGe Linux Operations
Sep 11, 2022 · Cloud Native

Can Eventual Consistency Boost Kubernetes Performance at the Edge?

This article examines how the strong‑consistency design of etcd limits Kubernetes scalability and latency in edge environments, presents experimental results on etcd performance, and proposes an eventual‑consistency storage layer to improve performance, availability, and scalability for edge deployments.

Container OrchestrationEdge computingKubernetes
0 likes · 25 min read
Can Eventual Consistency Boost Kubernetes Performance at the Edge?
IT Services Circle
IT Services Circle
Aug 24, 2022 · Databases

Data Consistency Between MySQL and Redis: Strategies and Best Practices

This article examines common pitfalls and six practical strategies for maintaining data consistency between MySQL and Redis caches, comparing naive approaches with optimal solutions such as cache double‑delete, asynchronous serialization via message queues, and binlog‑driven eventual consistency, and offers recommendations for real‑time and eventual consistency scenarios.

Cache ConsistencyDatabaseMessage Queue
0 likes · 8 min read
Data Consistency Between MySQL and Redis: Strategies and Best Practices
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Aug 6, 2022 · Backend Development

Why CQRS Matters: Evolving From Monolithic to Scalable Architecture

This article walks through the evolution of software design from a traditional monolithic API server to a CQRS-based architecture, highlighting the drawbacks of the anemic CRUD model, the benefits of read/write separation, domain messaging, eventual consistency, and practical implementation considerations.

DDDRead-Write Separationbackend development
0 likes · 9 min read
Why CQRS Matters: Evolving From Monolithic to Scalable Architecture
Baidu Geek Talk
Baidu Geek Talk
May 11, 2022 · Backend Development

Distributed Transactions: Concepts, TCC and Saga Patterns, and Practical Implementation

The article explains how micro‑service architectures create data‑consistency challenges that require distributed transaction strategies, compares strong‑consistency protocols like 2PC/3PC with eventual‑consistency approaches such as TCC and Saga patterns, and discusses their trade‑offs, implementation complexity, and suitability for real‑world scenarios like a points‑based sign‑in system.

MicroservicesSAGATCC
0 likes · 11 min read
Distributed Transactions: Concepts, TCC and Saga Patterns, and Practical Implementation
ITPUB
ITPUB
Dec 6, 2021 · Backend Development

Why ‘Insert‑Then‑Publish’ Isn’t Enough: Ensuring Reliable Message Delivery in Microservices

The article explains why the naïve "insert‑then‑publish" pattern can cause data inconsistency in microservice architectures, analyzes failure scenarios, and presents a local message‑table solution that leverages database transactions to achieve eventual consistency while handling duplicate messages.

Local Message Tabledistributed transactioneventual consistency
0 likes · 9 min read
Why ‘Insert‑Then‑Publish’ Isn’t Enough: Ensuring Reliable Message Delivery in Microservices
Architects Research Society
Architects Research Society
Dec 5, 2021 · Databases

Understanding Sequential, Causal, and Eventual Consistency Models

This article explains the concepts of sequential, causal, and eventual consistency models, illustrating their definitions, guarantees, and practical examples—including process interactions and real‑world scenarios—while comparing their strengths, trade‑offs, and related consistency guarantees such as monotonic reads, writes, and read‑your‑writes.

Databasescausal consistencyconsistency
0 likes · 10 min read
Understanding Sequential, Causal, and Eventual Consistency Models
DevOps
DevOps
Nov 17, 2021 · Cloud Native

Key Considerations for Microservice Migration: Dependency Management, Interface Versioning, Isolation, and Data Consistency

The article outlines essential practices for migrating to microservices, covering service dependency rules to avoid circular dependencies, interface version compatibility strategies, isolation techniques for data, deployment and business logic, and methods to ensure eventual data consistency using scheduled retries and transactional messaging.

Data IsolationMicroservicesService Dependency
0 likes · 14 min read
Key Considerations for Microservice Migration: Dependency Management, Interface Versioning, Isolation, and Data Consistency
Shopee Tech Team
Shopee Tech Team
Aug 26, 2021 · Databases

Database Architecture Evolution and Sharding Practice in Shopee's Logistics Service

Shopee’s Logistics Channel Service migrated from a shared‑cluster MySQL setup to dedicated clusters, added TiDB for transient tracking data, and ultimately adopted hash‑based sharding with separate order and tracking services plus an asynchronous compensation mechanism, enabling uniform data distribution, cross‑database consistency, six‑month archiving, and scalable growth without rebalancing.

Database ArchitectureMySQLTiDB
0 likes · 18 min read
Database Architecture Evolution and Sharding Practice in Shopee's Logistics Service
Wukong Talks Architecture
Wukong Talks Architecture
Aug 13, 2021 · Fundamentals

Reliable Message-Based Distributed Transaction Consistency Solution

This article explains the fundamentals of distributed transactions, introduces the reliable message eventual consistency approach, analyzes its challenges such as atomicity and message reliability, and presents two practical solutions—local message tables and RocketMQ transactional messages—along with their advantages and drawbacks.

Local Message TableRocketMQdistributed transactions
0 likes · 8 min read
Reliable Message-Based Distributed Transaction Consistency Solution
Architects Research Society
Architects Research Society
Apr 26, 2021 · Cloud Native

Asynchronous Messaging and Event‑Driven Communication in Microservices

This article explains the importance of asynchronous messaging and event‑driven communication for coordinating changes across multiple microservices and bounded contexts, covering single‑receiver and multi‑receiver patterns, message brokers, eventual consistency, publishing/subscribing mechanisms, and practical implementation considerations.

asynchronous messagingevent-driveneventual consistency
0 likes · 11 min read
Asynchronous Messaging and Event‑Driven Communication in Microservices
Wukong Talks Architecture
Wukong Talks Architecture
Feb 24, 2021 · Fundamentals

Understanding the Gossip Protocol Through a Virus Analogy

The article uses a whimsical story of a coronavirus‑like virus transmitted from a bat to humans to illustrate the Gossip protocol, its three functions—direct mail, anti‑entropy, and epidemic spread—and discusses their advantages, drawbacks, and practical applications in achieving eventual consistency in distributed systems.

Anti-entropyData Replicationdistributed systems
0 likes · 10 min read
Understanding the Gossip Protocol Through a Virus Analogy
360 Zhihui Cloud Developer
360 Zhihui Cloud Developer
Sep 9, 2020 · Databases

Understanding CAP, BASE, and Eventual Consistency: A Practical Guide

This article explains the CAP theorem, the trade‑offs among consistency, availability, and partition tolerance, introduces the BASE model and its properties, and details how different database systems implement various consistency guarantees such as strong, eventual, and causal consistency.

BASE modelCAP theoremConsistency trade‑offs
0 likes · 11 min read
Understanding CAP, BASE, and Eventual Consistency: A Practical Guide
Architect
Architect
Jun 18, 2020 · Backend Development

Applying Message Queues for Decoupling in E‑commerce Architecture

The article explains why and how to use message queues to achieve low‑coupling, better performance, fault tolerance, and eventual consistency in an e‑commerce order‑processing flow, discusses common pitfalls such as message loss and duplication, and compares popular queue products like RabbitMQ, Kafka, and RocketMQ.

Backend ArchitectureDecouplingKafka
0 likes · 10 min read
Applying Message Queues for Decoupling in E‑commerce Architecture
Architecture Digest
Architecture Digest
Apr 25, 2020 · Backend Development

Data Consistency Strategies in Microservices: Transaction Management Patterns

This article introduces the limitations of traditional local and distributed transactions for microservices, explains the BASE theory, and details four major patterns—reliable event notification, max‑effort notification, business compensation, and TCC—to achieve eventual consistency in microservice architectures.

Data ConsistencyMicroservicesTransaction Management
0 likes · 16 min read
Data Consistency Strategies in Microservices: Transaction Management Patterns
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Mar 31, 2020 · Backend Development

Mastering Distributed Transactions: Reliable Messaging, TCC, and Flexible Solutions

This article explores the fundamentals of distributed transactions, comparing traditional two‑phase commit with flexible approaches like reliable‑message eventual consistency, TCC, and best‑effort notification, and provides detailed design patterns, implementation steps, and trade‑offs for building robust backend systems.

2PCTCCbackend
0 likes · 19 min read
Mastering Distributed Transactions: Reliable Messaging, TCC, and Flexible Solutions
Architects Research Society
Architects Research Society
Jan 27, 2020 · Databases

CouchDB Final Consistency and Distributed System Design

This article explains CouchDB’s eventual consistency model, its use of MVCC, CAP theorem trade‑offs, incremental replication, and document validation, illustrating how these mechanisms enable scalable, high‑availability distributed databases without locking, and includes a practical case study of syncing Songbird playlists.

CouchDBMVCCdistributed systems
0 likes · 15 min read
CouchDB Final Consistency and Distributed System Design
Java High-Performance Architecture
Java High-Performance Architecture
May 15, 2019 · Databases

How to Achieve Distributed Transaction Consistency with Message Queues

This article explains how to handle distributed transactions in microservice architectures by using eventual consistency with message middleware, discusses the pitfalls of combining database updates and message sending in a single transaction, and presents a reliable solution involving a message table, background processing, ACK mechanisms, and deduplication.

IdempotencyMicroservicesdistributed transactions
0 likes · 5 min read
How to Achieve Distributed Transaction Consistency with Message Queues
Architecture Digest
Architecture Digest
Apr 1, 2019 · Backend Development

Seven Reliable Methods for Solving Distributed Transaction Problems

This article, excerpted from the book "Software Architecture Design: Integrating Large‑Scale Website Technical and Business Architecture," systematically presents seven practical solutions—including two eventual‑consistency approaches, two compromise methods, TCC, state‑machine retry with idempotence, and reconciliation—to address the pervasive challenges of distributed transactions in micro‑service systems.

2PCReconciliationTCC
0 likes · 25 min read
Seven Reliable Methods for Solving Distributed Transaction Problems
Programmer DD
Programmer DD
Jan 8, 2019 · Backend Development

How to Build a Reliable Message Service for Distributed Transactions

This article explains how to design and implement a reliable message service that ensures atomicity between upstream business transactions and downstream message delivery, using status management, callbacks, and scheduled tasks to achieve eventual consistency in distributed systems.

Message Queuedistributed transactionseventual consistency
0 likes · 9 min read
How to Build a Reliable Message Service for Distributed Transactions
Programmer DD
Programmer DD
Dec 26, 2018 · Backend Development

How Maximum‑Effort Notification Solves Distributed Transaction Challenges

This article explains the Maximum‑Effort Notification pattern for flexible distributed transactions, detailing its principles, workflow, implementation options, evaluation, and optimization techniques to achieve eventual consistency across services with limited retries and idempotent interfaces.

distributed transactionseventual consistencymaximum effort
0 likes · 11 min read
How Maximum‑Effort Notification Solves Distributed Transaction Challenges
Architects' Tech Alliance
Architects' Tech Alliance
Dec 10, 2018 · Fundamentals

Why Consistency Matters in Distributed Systems: A Deep Dive

This article explains the fundamental reasons for building distributed systems, examines the inevitable side‑effects—especially data consistency challenges—analyzes the root causes of inconsistency, and walks through various consistency models from eventual to linearizability with clear examples and illustrations.

Data ConsistencyLinearizabilitySystem Design
0 likes · 10 min read
Why Consistency Matters in Distributed Systems: A Deep Dive
21CTO
21CTO
Oct 17, 2018 · Databases

Scaling Payment Systems: Sharding, Snowflake IDs, and High‑Availability

This article explains how to design a high‑throughput payment system using database sharding, Snowflake‑style globally unique order IDs, eventual consistency via message queues, high‑availability architectures, data tiering, and coarse‑fine traffic control to handle massive request spikes.

Data TieringDatabaseSharding
0 likes · 15 min read
Scaling Payment Systems: Sharding, Snowflake IDs, and High‑Availability
Mike Chen's Internet Architecture
Mike Chen's Internet Architecture
Sep 23, 2018 · Fundamentals

Comparison of Mainstream Message Queue Products and Their Typical Use Cases

This article examines the core features, performance characteristics, and typical application scenarios of popular message queue middleware such as ZeroMQ, RabbitMQ, ActiveMQ, Redis, Kafka, and others, while also discussing when to adopt a message queue, its benefits like decoupling, eventual consistency, broadcasting, and flow control, and summarizing best‑practice guidelines.

MQ ComparisonMessage Queueasynchronous communication
0 likes · 13 min read
Comparison of Mainstream Message Queue Products and Their Typical Use Cases
JD Tech
JD Tech
Jun 11, 2018 · Backend Development

Message Queue (MQ) Usage Scenarios, Patterns, and Pitfalls

Message queues enable asynchronous, decoupled communication between systems, and this article explains core scenarios such as decoupling, peak‑shaving, achieving eventual consistency, broadcast consumption, and retry handling, while highlighting implementation details, pull‑mode code, and important considerations like idempotency and consumption monitoring.

BroadcastDecouplingIdempotency
0 likes · 10 min read
Message Queue (MQ) Usage Scenarios, Patterns, and Pitfalls
ITFLY8 Architecture Home
ITFLY8 Architecture Home
Oct 3, 2017 · Backend Development

Why Distributed Transactions Still Matter: Strategies Beyond 2PC

This article explores the challenges of distributed transactions in microservice architectures, explains consistency theories like CAP and BASE, compares classic 2PC with eBay's event‑queue approach, TCC compensation, and cache‑based eventual consistency, and offers practical guidance for choosing the right solution.

2PCBASECAP theorem
0 likes · 11 min read
Why Distributed Transactions Still Matter: Strategies Beyond 2PC
dbaplus Community
dbaplus Community
Apr 16, 2017 · Backend Development

Ensuring Data Consistency with Distributed Transactions: From Single DB to TCC

This article walks through the evolution of distributed transaction architectures—from simple single-database transactions, through post-commit multi-database approaches and two-phase commit, to TCC and eventual-consistency patterns—illustrating each method with game-style purchase examples, diagrams, and practical implementation tips.

TCCeventual consistencytwo-phase commit
0 likes · 15 min read
Ensuring Data Consistency with Distributed Transactions: From Single DB to TCC
21CTO
21CTO
Apr 15, 2017 · Backend Development

How to Design Distributed Transactions for Consistent Microservices

This article explains the principles of distributed transaction design, covering ACID fundamentals, typical banking and e‑commerce scenarios, various transaction models such as two‑phase, compensation, asynchronous and best‑effort notifications, and presents a micro‑service architecture with concrete flow diagrams and scaling strategies for a high‑throughput traffic‑recharge platform.

Data ConsistencyMicroservicesdistributed transactions
0 likes · 12 min read
How to Design Distributed Transactions for Consistent Microservices
Architecture Digest
Architecture Digest
Apr 6, 2017 · Fundamentals

Distributed Service System Consistency: Best Practices and Patterns

This article examines the challenges of achieving consistency in large‑scale distributed service systems, outlines common inconsistency scenarios such as split‑brain and lost updates, and presents practical patterns—including ACID/BASE trade‑offs, two‑phase and three‑phase commit, TCC, query, compensation, and reliable messaging—to guide engineers in designing robust, eventually consistent architectures.

ACIDBASEMicroservices
0 likes · 35 min read
Distributed Service System Consistency: Best Practices and Patterns
Architecture Digest
Architecture Digest
Apr 1, 2017 · Backend Development

Distributed Consistency and Transactional Messaging Solutions

This article explains the challenges of achieving consistency in distributed systems and presents practical solutions such as two‑phase commit, asynchronous assurance, compensating transactions, message retry mechanisms, idempotent designs, and a custom Redis‑based delayed queue (DelayQ) with a transactional proxy (TMQProxy) to provide reliable transactional messaging.

IdempotencyMessage RetryRedis delay queue
0 likes · 19 min read
Distributed Consistency and Transactional Messaging Solutions
Art of Distributed System Architecture Design
Art of Distributed System Architecture Design
Dec 2, 2016 · Backend Development

Mastering Distributed Transaction Consistency: From CAP to Message‑Based Compensation

This article examines the fundamental challenges of achieving consistency in distributed systems, explains the CAP theorem, compares two‑phase and three‑phase commit protocols, explores XA transactions, and presents practical compensation patterns such as local message tables, non‑transactional and transactional MQ designs, highlighting their trade‑offs and applicability.

CAP theoremMessage QueueMicroservices
0 likes · 15 min read
Mastering Distributed Transaction Consistency: From CAP to Message‑Based Compensation
Qunar Tech Salon
Qunar Tech Salon
Apr 26, 2016 · Databases

Distributed Transaction and Data Consistency Solutions for E‑commerce Systems

The article examines the challenges of maintaining data consistency across distributed services in e‑commerce, explains strong, weak and eventual consistency models, and presents six practical solutions—including business integration, the eBay BASE pattern, Qunar, Mogujie, Alipay DTS, and Nongxin—highlighting how local transactions, idempotent messaging, and eventual consistency can replace heavyweight distributed‑transaction frameworks.

BASEData ConsistencyMicroservices
0 likes · 16 min read
Distributed Transaction and Data Consistency Solutions for E‑commerce Systems
High Availability Architecture
High Availability Architecture
Apr 19, 2016 · Databases

Distributed Transaction Consistency Solutions for E‑commerce Systems

This article explains the challenges of maintaining data consistency across multiple services in distributed e‑commerce architectures and presents six practical solutions—including business integration, the eBay BASE pattern, Qunar's approach, Mogujie's design, Alipay's DTS, and Nongxin's scheme—highlighting their advantages, drawbacks, and implementation details.

BASECAP theoremData Consistency
0 likes · 16 min read
Distributed Transaction Consistency Solutions for E‑commerce Systems