etcd/Documentation
Roy Lenferink eb42a5cb2f Documentation: Deleted non-existing project from libraries-and-tools.md 2017-01-25 11:43:56 -05:00
..
benchmarks hack/benchmark: change boom to hey 2016-10-24 13:28:53 -07:00
dev-guide *: regenrate proto files with 'ignore_lease' 2017-01-25 03:01:47 +05:30
dev-internal scripts, doc: remove actool references 2016-09-06 17:47:41 +02:00
learning why: add origin of the term etcd 2017-01-06 16:12:20 -06:00
op-guide op-guide: change grpc-proxy from 'pre' to alpha' 2017-01-20 13:20:32 -08:00
platforms doc: Update freebsd.md 2016-02-18 23:03:19 -06:00
rfc *: rename storage package to mvcc 2016-04-25 15:25:51 -07:00
upgrades Merge pull request #7155 from andrewstuart/upgrade-etcd3-docs 2017-01-21 12:56:07 -08:00
v2 Polish note about varying parameters for each member 2017-01-18 14:55:02 -08: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: mention HTTP JSON in doc link 2017-01-22 10:55:21 -08:00
faq.md Documentation: add FAQs on membership operation 2016-12-16 15:13:40 -08:00
libraries-and-tools.md Documentation: Deleted non-existing project from libraries-and-tools.md 2017-01-25 11:43:56 -05:00
metrics.md op-guide: update gRPC requests metrics 2016-11-14 15:20:16 -08:00
production-users.md Documentation: conform to header style 2016-06-27 12:00:24 -07:00
reporting_bugs.md Documentation: conform to header style 2016-06-27 12:00:24 -07:00
tuning.md Documentation: tuning advice for peer prioritization 2016-07-07 19:14:31 -07: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.