Tagged articles
BASE theory
26 articles · Page 1 of 1

liandkSep 30, 2026 · Backend Development
This article provides a comprehensive guide to distributed transactions in microservices, covering CAP/BASE theory, four major patterns (2PC, local message table, TCC, SAGA), eight common production faults with root causes and fixes, selection guidelines, a troubleshooting SOP, and high-availability standards.
2PCBASE theoryCAP theorem
0 likes · 19 min read

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

This article examines the limitations of the CAP theorem in modern microservice architectures, introduces the BASE model for eventual consistency, and evaluates practical solutions such as write RPC retries, synchronous and transactional messaging, and local message tables to achieve reliable data consistency across distributed services.
BASE theoryCAP theoremDistributed Consistency
0 likes · 11 min read

This article explains the role of consensus algorithms in achieving high‑availability through redundancy and automatic failover, clarifies distributed consistency, explores the CAP theorem and its C component, and introduces the BASE theory as a practical complement for eventual consistency in modern distributed systems.
BASE theoryCAP theoremConsensus
0 likes · 10 min read

To address consistency problems in distributed systems, the article explains CAP and BASE trade‑offs, shows how transactional RPC and messaging—using retries, RocketMQ two‑phase commits, Spring @TransactionalEventListener, or a local message log—can ensure atomic updates, and compares their reliability, latency, and performance impacts.
BASE theoryCAP theoremDistributed Consistency
0 likes · 12 min read


政采云技术Apr 27, 2023 · Backend Development
This article explains the CAP theorem and its trade‑offs, introduces the BASE model as a practical compromise, and demonstrates how Zookeeper implements a CP registration center while Eureka adopts an AP approach, illustrating the impact on consistency, availability, and partition tolerance in distributed systems.
BASE theoryCAP theoremConsistency
0 likes · 12 min read


ITPUBApr 13, 2023 · Fundamentals
This article explains distributed transactions, the reasons they arise, the CAP and BASE theories that guide consistency trade‑offs, and outlines strong, eventual, and weak consistency solutions along with popular frameworks for implementing them in modern distributed systems.
BASE theoryCAP theoryconsistency models
0 likes · 11 min read

This article explains the basic concepts of transactions, distinguishes local and distributed transactions, introduces the CAP and BASE theories, and compares major distributed‑transaction solutions such as 2PC, XA, Seata, TCC, reliable‑messaging and maximum‑effort notification, highlighting their trade‑offs.
2PCBASE theoryBackend
0 likes · 40 min read

This article explains the fundamentals of transactions, the challenges of distributed transactions, introduces ACID, CAP and BASE theories, and compares practical solutions such as two‑phase commit, TCC, Seata, reliable message‑based eventual consistency, and maximum‑effort notification, concluding with a comparative analysis of their trade‑offs.
2PCBASE theoryCAP theorem
0 likes · 42 min read

This article explains the evolution from centralized to distributed architectures, the role of Zookeeper in solving consistency problems, the mechanics and drawbacks of 2‑phase and 3‑phase commits, and key consensus algorithms such as Paxos, Raft, ZAB, as well as CAP and BASE theories that guide practical system design.
2PC3PCBASE theory
0 likes · 23 min read

This article explores the challenges of distributed transactions, explains database ACID fundamentals, introduces CAP and BASE theories, compares solutions such as two‑phase commit, TCC, local message tables, MQ transactional messages, and the Sagas model, and presents the open‑source .NET CAP framework with its features and implementation details.
.NET CAP2PCBASE theory
0 likes · 17 min read

This article explains the evolution of backend service architectures, introduces the CAP and BASE theories, and provides detailed walkthroughs of the Paxos and Raft consensus algorithms, covering their roles, constraints, protocol steps, and practical considerations for building reliable distributed systems.
BASE theoryCAP theoryConsensus Algorithm
0 likes · 22 min read

This article provides a comprehensive technical guide to distributed transactions, covering ACID fundamentals, consistency models, sharding techniques, CAP and BASE theories, and detailed implementations of two‑phase, three‑phase, and TCC protocols, while highlighting their advantages, limitations, and practical considerations.
BASE theoryCAP theoremSharding
0 likes · 23 min read

From CAP and BASE trade‑offs to the rigorous Paxos consensus and the more approachable Raft protocol, this article explains how modern distributed systems achieve consistency despite partitions, failures, and latency, detailing roles, phases, and safety guarantees that underpin reliable micro‑service architectures.
BASE theoryCAP theoremConsistency
0 likes · 21 min read

This article analyzes the challenges of distributed transactions in microservice architectures, explains ACID, CAP and BASE theories, compares consistency models, and evaluates practical solutions such as two‑phase commit, local message tables, TCC, and reliable messaging with code examples and implementation details.
2PCBASE theoryCAP theorem
0 likes · 26 min read

This article introduces the limitations of traditional local and distributed transactions for microservices, explains the BASE theory, and details four practical patterns—reliable event notification, maximum‑effort notification, business compensation, and TCC—providing code examples, diagrams, and a comparative table to guide developers in achieving eventual consistency across microservice architectures.
BASE theoryData ConsistencyTCC
0 likes · 19 min read

The article reviews microservice data consistency challenges, explains why traditional distributed transactions like 2PC/3PC are unsuitable, introduces the BASE theory, and details four implementation patterns—reliable event notification, maximum effort notification, business compensation, and TCC—to achieve eventual consistency.
BASE theoryData ConsistencyTCC
0 likes · 19 min read

Microservice architectures struggle with traditional ACID transactions, so this article reviews local and distributed transaction basics, explains why 2PC/3PC are unsuitable, introduces the BASE model, and details four practical consistency patterns—reliable event, async event, business compensation, and TCC—highlighting their mechanisms, advantages, and drawbacks.
BASE theoryData ConsistencyTCC
0 likes · 17 min read

This article explains the key characteristics of distributed systems, introduces the CAP and BASE theories, compares strong, weak and eventual consistency models, and reviews common distributed transaction solutions such as two‑phase commit, TCC and message‑based approaches, highlighting their trade‑offs and practical considerations.
BASE theoryCAP theoremTCC
0 likes · 13 min read

This article explains the rise of NoSQL databases, the CAP theorem and its CP/AP trade‑offs, critiques of CAP, and the BASE model, illustrating concepts with examples such as HBase and discussing how these principles guide modern distributed data systems.
BASE theoryCAP theoremConsistency
0 likes · 11 min read


21CTONov 26, 2019 · Fundamentals
This article explains the fundamentals of distributed transactions, compares local and global transaction models, examines protocols like XA and 2PC, introduces flexible transaction patterns such as TCC and compensable operations, and evaluates reliable message‑based solutions for achieving eventual consistency.
BASE theoryTCCTwo-Phase Commit
0 likes · 15 min read

This article explains the CAP theorem, the trade‑offs among consistency, availability and partition tolerance, describes strong, weak and eventual consistency models, and introduces the BASE approach as a practical alternative for large‑scale distributed systems.
BASE theoryCAP theoremConsistency
0 likes · 12 min read

This article explains why transactions are essential, traces their origin from early XA specifications, examines the CAP and BASE theories that expose challenges in distributed systems, and reviews practical solutions such as two‑phase commit, three‑phase commit, TCC, asynchronous messaging, Saga and Gossip protocols, highlighting their trade‑offs and when to apply each.
BASE theoryCAP theoremSaga pattern
0 likes · 17 min read

The article explains the necessity of transactions, traces their origins from database XA specifications to modern distributed systems, compares CAP and BASE theories, and reviews mainstream solutions such as two‑phase commit, three‑phase commit, TCC, asynchronous messaging, and the Saga pattern.
BASE theoryCAP theoremSaga pattern
0 likes · 14 min read

This article explains the evolution and core concepts of mainstream distributed architectures—including SOA, microservices, and service mesh—covers fundamental consistency theories such as CAP and BASE, and outlines practical high‑availability and scalability techniques for building resilient cloud‑native systems.
BASE theoryCAP theoremHigh Availability
0 likes · 17 min read

This article explores the importance of data consistency in distributed systems, illustrating real‑world scenarios, explaining consistency models such as strong, weak and eventual, and detailing the challenges and theories like CAP and BASE that guide system designers in balancing consistency, availability, and partition tolerance.
BASE theoryCAP theoremConsistency
0 likes · 18 min read
