LOlongdeqidao·Aug 30, 2019Submission
2 points · Open discussionetcd-io
etcd
Go2013–2024
etcd-io / etcd
etcd
Distributed reliable key-value store for the most critical data of a distributed system
79Distinct people
108Mentions
0Explicit recommenders
52.6KGitHub stars
What to know before exploring
What it is
Distributed reliable key-value store for the most critical data of a distributed system
GitHub
Where it is used
- Fidelity Investments — “We use CoreDNS for service discovery, etcd as KV store, Fluentd for logging, Helm as a package manager, Kubernetes for container orchestration, rely on CNI …” Source
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- hashicorp/consul · linked in 2 of the same discussions
- influxdata/influxdb · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year108 dated mentions
Observed mentions: 2013-07-31 15:48:56 UTC to 2024-11-28 01:23:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 11 | 2 | 9 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 13 | 0 | 13 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 20 | 2 | 18 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 15 | 0 | 15 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 12 | 0 | 12 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 4 | 2 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 7 | 0 | 7 |
What Hacker News says
6 sourcesIt's sort of like a SQL version of etcd, so maybe some of the use cases for etcd would be similar: https://github.com/etcd-io/etcd/blob/master/Documentation/pr...
In Dqlite – High-Availability SQLiteThe performance of the etcd system is complex[1], there’s raft consensus, replication, security, snapshots, networking, and basically a lot going on.
Perhaps, your benchmarks really do reflect problems that go has with gc, but perhaps some other part amonst the numerous moving parts are causing the poor benchmark results. I’m not sure that we can conclude from your results that go has gc problems when the heap is large.
[1] https://github.com/etcd-io/etcd/blob/master/Documentation/op...
In Go Creeping InAlternatively the K3s authors could have embedded a single node etcd process into Kubernetes using the embed package instead of introducing sqlite.
https://godoc.org/github.com/etcd-io/etcd/embed
This is something the Kubernetes community might consider as well.
In K3s – Lightweight KubernetesAlternatively the K3s authors could have embedded a single node etcd process into Kubernetes using the embed package instead of introducing sqlite.
https://godoc.org/github.com/etcd-io/etcd/embed
This is something the Kubernetes community might consider as well.
In K3s – Lightweight KubernetesFor paxos, this explains it very well (while you are likely to require multi-paxos): https://understandingpaxos.wordpress.com/
For Raft, comparing it with paxos, it is simple, but in general, it isn't a simple protocol, there are several details to take care of.
Edit: There is a great raft implementation in go (https://github.com/etcd-io/etcd).
In Recommendations for a Paxos consensus protocol implementation in Golang