|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Etcd||43,644||4,048||2,314||15 hours ago||396||April 24, 2022||215||apache-2.0||Go|
|Distributed reliable key-value store for the most critical data of a distributed system|
|Ddia||17,643||a day ago||cc-by-4.0||Python|
|《Designing Data-Intensive Application》DDIA中文翻译|
|Rqlite||13,752||3||2||3 days ago||42||April 14, 2021||54||mit||Go|
|The lightweight, distributed relational database built on SQLite|
|Zookeeper||11,334||2 days ago||1||December 18, 2019||226||apache-2.0||Java|
|Nebula||9,140||1||19 hours ago||1||December 17, 2019||445||apache-2.0||C++|
|A distributed, fast open-source graph database featuring horizontal scalability and high availability|
|Trino||7,941||3||9||15 hours ago||51||December 29, 2020||2,335||apache-2.0||Java|
|Official repository of Trino, the distributed SQL query engine for big data, formerly known as PrestoSQL (https://trino.io)|
|Realtime||5,900||2 days ago||2||May 01, 2021||20||apache-2.0||Elixir|
|Broadcast, Presence, and Postgres Changes via WebSockets|
|Tendermint||5,499||238||1,264||23 days ago||717||September 08, 2022||385||apache-2.0||Go|
|⟁ Tendermint Core (BFT Consensus) in Go|
|Materialize||5,145||14 hours ago||2||August 12, 2022||2,028||other||Rust|
|Materialize is a fast, distributed SQL database built on streaming internals.|
|Encore||3,780||2 days ago||40||September 21, 2022||40||mpl-2.0||Go|
|Encore is the end-to-end Backend Development Platform that lets you escape cloud complexity.|
main branch may be in an unstable or even broken state during development. For stable versions, see releases.
etcd is a distributed reliable key-value store for the most critical data of a distributed system, with a focus on being:
etcd is written in Go and uses the Raft consensus algorithm to manage a highly-available replicated log.
etcd is used in production by many companies, and the development team stands behind it in critical deployment scenarios, where etcd is frequently teamed with applications such as Kubernetes, locksmith, vulcand, Doorman, and many others. Reliability is further ensured by rigorous robustness testing.
See etcdctl for a simple command line client.
Original image credited to xkcd.com/2347, alterations by Josh Berkus.
MAINTAINERS strive to shape an inclusive open source project culture where users are heard and contributors feel respected and empowered. MAINTAINERS maintain productive relationships across different companies and disciplines. Read more about MAINTAINERS role and responsibilities.
The easiest way to get etcd is to use one of the pre-built release binaries which are available for OSX, Linux, Windows, and Docker on the release page.
For more installation guides, please check out play.etcd.io and operating etcd.
First start a single-member cluster of etcd.
If etcd is installed using the pre-built release binaries, run it from the installation location as below:
The etcd command can be simply run as such if it is moved to the system path as below:
mv /tmp/etcd-download-test/etcd /usr/local/bin/ etcd
This will bring up etcd listening on port 2379 for client communication and on port 2380 for server-to-server communication.
Next, let's set a single key, and then retrieve it:
etcdctl put mykey "this is awesome" etcdctl get mykey
etcd is now running and serving client requests. For more, please check out:
The official etcd ports are 2379 for client requests, and 2380 for peer communication.
First install goreman, which manages Procfile-based applications.
Our Procfile script will set up a local example cluster. Start it with:
This will bring up 3 etcd members
infra3 and optionally etcd
grpc-proxy, which runs locally and composes a cluster.
Every cluster member and proxy accepts key value reads and key value writes.
Follow the steps in Procfile.learner to add a learner node to the cluster. Start the learner node with:
goreman -f ./Procfile.learner start
go get go.etcd.io/etcd/client/v3
Now it's time to dig into the full etcd API and other guides.
etcd contributors and maintainers have monthly (every four weeks) meetings at 11:00 AM (USA Pacific) on Thursday.
An initial agenda will be posted to the shared Google docs a day before each meeting, and everyone is welcome to suggest additional topics or other agendas.
Meeting recordings are uploaded to official etcd YouTube channel.
Get calendar invitation by joining etcd-dev mailing group.
Join Hangouts Meet: meet.google.com/umg-nrxn-qvs
Join by phone: +1 405-792-0633 PIN: 299 906#
See CONTRIBUTING for details on setting up your development environment, submitting patches and the contribution workflow.
Please refer to community-membership.md for information on becoming an etcd project member. We welcome and look forward to your contributions to the project!
See reporting bugs for details about reporting any issues. Before opening an issue please check it is not covered in our frequently asked questions.
See security disclosure and release process for details on how to report a security vulnerability and how the etcd team manages it.
See issue triage guidelines for details on how issues are managed.
See PR management for guidelines on how pull requests are managed.
These emeritus maintainers dedicated a part of their career to etcd and reviewed code, triaged bugs and pushed the project forward over a substantial period of time. Their contribution is greatly appreciated.
etcd is under the Apache 2.0 license. See the LICENSE file for details.