Tagged articles
4 articles
Page 1 of 1
Wukong Talks Architecture
Wukong Talks Architecture
Mar 23, 2022 · Backend Development

Understanding Zookeeper's ZAB Protocol: Leader Election, Data Synchronization, and Consistency

This article explains Zookeeper's ZAB (Zookeeper Atomic Broadcast) protocol, detailing node roles, the leader election process during startup and failure, the two‑phase commit data synchronization, ordering guarantees, and scenarios of leader crash and data loss, providing clear diagrams and code examples.

ConsensusDistributed SystemsZAB
0 likes · 10 min read
Understanding Zookeeper's ZAB Protocol: Leader Election, Data Synchronization, and Consistency
Ops Development Stories
Ops Development Stories
Apr 5, 2021 · Fundamentals

Understanding ZAB: How ZooKeeper Guarantees Strong Consistency

This article explains the ZAB (ZooKeeper Atomic Broadcast) protocol, detailing its atomic broadcast mechanism, two‑phase commit style messaging, transaction IDs (ZXID), leader‑follower coordination, crash recovery principles, data synchronization, and the underlying ZXID design with illustrative code snippets.

ZABatomic broadcastcrash recovery
0 likes · 11 min read
Understanding ZAB: How ZooKeeper Guarantees Strong Consistency
Architect's Tech Stack
Architect's Tech Stack
Mar 19, 2019 · Fundamentals

Understanding ZAB: The Zookeeper Atomic Broadcast Protocol

This article explains the ZAB protocol—Zookeeper's atomic broadcast and crash‑recovery mechanism—detailing its design, message‑broadcast process, leader election, transaction ordering with ZXID, and how it ensures data consistency and availability in distributed systems.

ConsensusZABZooKeeper
0 likes · 8 min read
Understanding ZAB: The Zookeeper Atomic Broadcast Protocol
WeChat Backend Team
WeChat Backend Team
Sep 8, 2016 · Databases

Why PhxSQL Rejects Multi-Write, Sharding, and Serializability: Design Trade‑offs

This article explains how PhxSQL prioritizes strong linearizable consistency, high availability, serializable isolation, and full MySQL compatibility, and why it deliberately forgoes features such as multi‑write, sharding, and strict serializable isolation due to the high cost of distributed transactions and protocol complexity.

ConsistencyMySQL compatibilityPhxSQL
0 likes · 17 min read
Why PhxSQL Rejects Multi-Write, Sharding, and Serializability: Design Trade‑offs