etcd/Documentation
Elijah C. Voigt 31c1931b7b Docs: replace absolute links with relative ones. 2017-04-04 15:21:42 -07:00
..
benchmarks Docs: replace absolute links with relative ones. 2017-04-04 15:21:42 -07:00
dev-guide *: use protoc 3.2.0 2017-03-30 13:43:10 -07:00
dev-internal Documentation: sign source zip files 2017-03-08 11:53:52 -08:00
learning Documentation: fix typos 2017-03-30 11:41:50 +03:00
op-guide Docs: replace absolute links with relative ones. 2017-04-04 15:21:42 -07:00
platforms *: eschew you from documentation 2017-03-06 11:40:46 -08:00
rfc *: rename storage package to mvcc 2016-04-25 15:25:51 -07:00
upgrades Documentation: warn membership change while migration 2017-03-07 11:27:36 -08:00
v2 Docs: replace absolute links with relative ones. 2017-04-04 15:21:42 -07:00
README.md documentation: display docs.md in github browser 2017-01-11 10:37:42 -08:00
branch_management.md Documentation: conform to header style 2016-06-27 12:00:24 -07:00
demo.md Documentation/demo: add member, auth example 2016-06-23 11:50:37 -07:00
dl_build.md documentation: update build documentation 2017-01-20 11:04:40 -08:00
docs.md doc: link auth design in doc 2017-03-27 11:58:32 -07:00
faq.md Documentation: add disk latency leader loss question to FAQ 2017-03-28 15:49:21 -07:00
integrations.md Documentation: add dims v3 gateway API for python 2017-04-03 12:55:24 -07:00
metrics.md op-guide: update gRPC requests metrics 2016-11-14 15:20:16 -08:00
production-users.md Documentation: add salesforce to prod users 2017-03-23 12:29:37 -07:00
reporting_bugs.md Documentation: conform to header style 2016-06-27 12:00:24 -07:00
tuning.md Documentation: suggest ionice for disk tuning 2017-03-02 13:58:07 -08:00

README.md

Documentation

etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.

Getting started

New etcd users and developers should get started by downloading and building etcd. After getting etcd, follow this quick demo to see the basics of creating and working with an etcd cluster.

Developing with etcd

The easiest way to get started using etcd as a distributed key-value store is to set up a local cluster.

Operating etcd clusters

Administrators who need to create reliable and scalable key-value stores for the developers they support should begin with a cluster on multiple machines.

Learning

To learn more about the concepts and internals behind etcd, read the following pages:

Upgrading and compatibility

Frequently Asked Questions (FAQ)

Answers to common questions about etcd.