etcd: A distributed reliable key-value store for the most critical data of a distributed system.
What problem it solves
Distributed systems need a reliable place to store critical data and coordinate access to it. The project addresses this with a well-defined API, replication through Raft, and security features such as automatic TLS.
Key features
Well-defined gRPC API — The user-facing API is designed to be simple and is provided through gRPC.
Source: README
Secure client communication — Cluster communication supports TLS, with optional authentication through client certificates.
Source: README
Raft-based replication — The Raft consensus algorithm manages a highly available replicated log across distributed members.
Source: README
Local cluster tooling — A Procfile-based setup can start a local three-member cluster and an optional gRPC proxy.
Source: README, Procfile
Robustness testing — The project includes a dedicated robustness-testing area to support reliability assurance.
Source: README, tests
Quick start
Copied verbatim from the project's README.
/tmp/etcd-download-test/etcdetcdctl put mykey "this is awesome"
etcdctl get mykeygo get go.etcd.io/etcd/client/v3Who it may suit
This may suit developers and operators building distributed systems that need reliable replicated key-value storage or a local cluster for experimentation.
Topics to discuss
How should teams balance the simplicity of the gRPC API with their operational requirements?
What practices are most effective for securing etcd clusters in production environments?
Which community improvements would be most valuable for robustness testing and cluster operations?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/etcd-io/etcd#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…