Search across authors, categories, and technical themes. The layout mirrors the editorial references while staying responsive and fast.
This article explains the fundamentals of Raft and PBFT consensus algorithms, compares their processes, fault tolerance limits, and suitability for private and consortium blockchains, and highlights key differences in leader election, message handling, and fault models.
This article provides an in‑depth exploration of distributed consensus protocols, detailing the basics of Paxos, extending to Multi‑Paxos, and comparing it with Raft and Zab while discussing leader election, quorum, lease mechanisms, and practical considerations for implementing these algorithms in real‑world systems.
This article explores how to build fault‑tolerant distributed systems by formalizing consensus, outlines its core properties, explains the FLP impossibility theorem, and shows how algorithms like Raft sidestep its limits through timing constraints and recovery mechanisms.
Kafka 4.0 replaces ZooKeeper with the native KRaft (Kafka Raft) consensus layer, simplifying deployment, boosting scalability, cutting latency, and introducing a new incremental consumer rebalance protocol and share‑group model that together reshape how distributed streaming applications are built and operated.
This article explains Nacos, Alibaba's dynamic naming and configuration service, covering its architecture, service registration and discovery mechanisms, Raft‑based consistency, and configuration management with long‑polling, providing a comprehensive overview for microservice practitioners.
This article provides a comprehensive overview of Apache RocketMQ, detailing its core components, producer and consumer workflows, storage strategies, master‑slave synchronization, Raft‑based half‑write and leader election mechanisms, and best‑practice recommendations for high‑throughput, fault‑tolerant messaging systems.
DingoDB is a multi‑modal vector database that unifies storage and analysis of structured, semi‑structured and unstructured data through a Raft‑based distributed architecture, offering MySQL‑compatible SQL, high‑performance APIs, automatic sharding, real‑time index optimization, and hybrid scalar‑vector queries for enterprise knowledge bases, LLM memory, and real‑time decision‑making.
This article explains the high‑availability architecture of TuGraph‑DB, covering the concepts of HA, the Raft consensus algorithm, cluster design, server and client mechanisms, snapshot handling, and future roadmap such as witness nodes and on‑demand snapshots.
The article explains why traditional MySQL sharding is discouraged, introduces the distributed database TiDB, details its architecture, core capabilities such as HTAP and Raft‑based consistency, compares feature support and resource usage with MySQL, and presents benchmark results demonstrating TiDB’s advantages at large scale.
Distributed leader election ensures a single node performs exclusive tasks in high‑availability systems, with common implementations like Etcd, Kafka, Elasticsearch, and Zookeeper using algorithms such as Paxos, Raft, and ZAB, while Kubernetes provides the Lease resource to manage leader election via a distributed lock.