![]() doc/learning: complete the api guide |
||
---|---|---|
.. | ||
benchmarks | ||
dev-guide | ||
dev-internal | ||
learning | ||
op-guide | ||
platforms | ||
rfc | ||
upgrades | ||
v2 | ||
README.md | ||
branch_management.md | ||
demo.md | ||
dl_build.md | ||
docs.md | ||
faq.md | ||
integrations.md | ||
metrics.md | ||
production-users.md | ||
reporting_bugs.md | ||
tuning.md |
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.
- Setting up local clusters
- Interacting with etcd
- gRPC API references
- HTTP JSON API through the gRPC gateway
- gRPC naming and discovery
- Embedding etcd
- Experimental features and APIs
- System limits
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.
- Setting up etcd clusters
- Setting up etcd gateways
- Setting up etcd gRPC proxy (pre-alpha)
- Run etcd clusters inside containers
- Hardware recommendations
- Configuration
- Security
- Monitoring
- Maintenance
- Understand failures
- Disaster recovery
- Performance
- Versioning
- Supported platform
Learning
To learn more about the concepts and internals behind etcd, read the following pages:
- Why etcd (TODO)
- Understand data model
- Understand APIs
- Glossary
- Internals (TODO)
Upgrading and compatibility
Frequently Asked Questions (FAQ)
Answers to common questions about etcd.