What Is etcd? Features, Use Cases, and Comparison with Zookeeper

etcd (pronounced /ˈɛtsiːdiː/) stands for "distributed etc directory" and serves as a reliable, distributed key‑value store for critical configuration data in large distributed systems.

The official description calls it "a distributed, reliable key‑value store for the most critical data of a distributed system," emphasizing its role as a coordination service that stores a small amount of data fully in memory.

Inspired by Zookeeper and doozer, etcd offers four main advantages: simple HTTP+JSON API, optional SSL client authentication, high write throughput (about 1,000 writes per second per instance), and strong consistency via the Raft algorithm.

etcd has become popular through projects like CoreOS and Kubernetes, addressing the need for fast, transparent service registration, configuration discovery, and high‑availability clusters in cloud‑native environments.

Application scenarios:

Service discovery: registers services with TTL keys, monitors health via watchers, and enables dynamic service addition in micro‑service architectures.

Message publish/subscribe: stores configuration and metadata, uses watchers for real‑time updates, and supports distributed logging and search index coordination.

Load balancing: leverages etcd’s distributed architecture to store small, frequently accessed data such as secondary code tables and to maintain node status tables for round‑robin routing.

Distributed notification & coordination: uses watchers to implement low‑coupling heartbeat detection, system scheduling, and work progress reporting.

Distributed lock: provides atomic CompareAndSwap operations with prevExist and ordered keys via POST to implement exclusive locks and sequencing.

Distributed queue: creates FIFO queues under directories like /queue and uses a /queue/condition node to control execution based on custom conditions.

Cluster monitoring & leader election: employs TTL keys and watchers to detect node health, and uses Raft‑based CAS mechanisms to elect a leader for tasks such as full‑index building.

Why choose etcd over Zookeeper: etcd is simpler to deploy (written in Go, HTTP API), offers built‑in persistence, SSL security, and benefits from rapid development, while Zookeeper suffers from complex deployment, Java‑centric tooling, and slower evolution.

Overall, etcd is a lightweight, reliable, and secure component widely adopted by CoreOS, Kubernetes, Cloud Foundry, and other production systems, making it a valuable tool for modern cloud‑native architectures.