[Notes]: etcd Internals

Prelude

For now, mostly just some cool articles that were very helpful in understanding etcd internals.

Notes

• etcd first sends transaction requests to it’s Raft engine. This effectively serves as a write-ahead log. Once consensus on the transaction is reached, the transaction is committed to etcd’s underlying key-vale store.

• etcd uses bbolt as its durable store, which is based on a B+ tree variation

• etcd will persist Raft cluster information/membership in it’s storage backend

  • Old pointer to older code from the mailing list

Useful references

• Michael Gasch - Onwards to the Core: etcd
• Pierre Zemb - Notes about ETCD
• Dmitry Dolgov - Evolution of tree data structures for indexing: more exciting than it sounds
• Michelle Nguyen - How etcd works and 6 tips to keep in mind