Tagged articles
Transaction Consistency
12 articles · Page 1 of 1
This article provides a step-by-step methodology for splitting bounded contexts after event storming, covering four golden rules (transaction consistency, change frequency, semantic uniqueness, team boundaries), an e-commerce case study, communication patterns, common pitfalls, and a mapping formula from contexts to microservices.
Anti-Corruption LayerDDD ModelingEvent Storming
0 likes · 15 min read

This article dissects the core processes, functional challenges, and architectural design of a high‑throughput, strongly consistent e‑commerce order system, covering forward and reverse flows, order creation, payment, fulfillment, cancellation, after‑sale handling, and the layered backend architecture that powers it.
Transaction Consistencybackend architecturedistributed systems
0 likes · 21 min read

Using a local message table, developers can break down distributed transactions into local database operations and asynchronous MQ messages, ensuring eventual consistency, simplifying implementation, and handling retries, while balancing advantages like simplicity and compatibility against drawbacks such as added maintenance and potential queue dependencies.
Message QueueTransaction Consistencybackend architecture
0 likes · 5 min read

The article explains why MySQL raises a GTID consistency error when a single transaction updates both InnoDB and MyISAM tables, demonstrates how to reproduce the issue, and evaluates three mitigation strategies: separating the updates, converting MyISAM to InnoDB, or disabling ENFORCE_GTID_CONSISTENCY.
GTIDInnoDBMyISAM
0 likes · 6 min read

Tencent Cloud's TDSQL team systematically proves that data anomalies are infinite, defines them formally, classifies them into three core types and detailed sub‑types, and releases an open‑source mini‑program for precise detection, advancing concurrency control theory and practice.
TDSQLTransaction Consistencydata anomalies
0 likes · 6 min read


58 TechJan 22, 2021 · Backend Development
This article explains how 58 Recruitment’s ETX framework applies CAP and BASE theories, along with log‑first and TCC patterns, to achieve distributed eventual consistency and high availability for large‑scale transaction processing in backend systems.
BASECAP theoremETX framework
0 likes · 8 min read

The article explains how to maintain transaction consistency between a primary database and sharded tables by using a flow‑log table and an asynchronous processor that ensures eventual consistency, handles ordering, retries, and avoids the complexity of transactional message queues.
ShardingTransaction Consistencydistributed systems
0 likes · 9 min read

This article explains how database sharding in micro‑service architectures creates transaction consistency problems and demonstrates a RocketMQ‑based solution that uses a two‑phase message workflow, state checks, and a Transaction table to achieve reliable distributed transactions.
RocketMQTransaction Consistencydistributed transaction
0 likes · 8 min read

This article explains why banks should adopt blockchain systems, outlines three guiding principles, describes typical integration architectures, examines changes to reconciliation and transaction consistency, and offers practical solutions for identity verification, key management, and high‑availability deployment.
BlockchainTransaction Consistencyarchitecture
0 likes · 12 min read

The article examines the reliability challenges of microservice architectures that rely heavily on synchronous RPC calls, and proposes a comprehensive solution that converts failing RPCs to asynchronous message‑queue workflows, introduces a write‑ahead‑queue for transactional consistency between databases and queues, and outlines offset management to ensure end‑to‑end fault tolerance.
KafkaMessage QueueRPC
0 likes · 12 min read


21CTOJul 25, 2017 · Fundamentals
This article explains distributed system fundamentals—CAP theorem, ACID properties, consistency models, and how 2PC and 3PC protocols, along with message‑middleware solutions like RocketMQ, address the challenges of achieving reliable complex distributed transactions.
2PC3PCACID
0 likes · 14 min read

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 QueueTransaction Consistency
0 likes · 15 min read
