1**This is the documentation for etcd2 releases. Read [etcd3 doc][v3-docs] for etcd3 releases.** 2 3[v3-docs]: ../docs.md#documentation 4 5 6# Production Users 7 8This document tracks people and use cases for etcd in production. By creating a list of production use cases we hope to build a community of advisors that we can reach out to with experience using various etcd applications, operation environments, and cluster sizes. The etcd development team may reach out periodically to check-in on your experience and update this list. 9 10## discovery.etcd.io 11 12- *Application*: https://github.com/coreos/discovery.etcd.io 13- *Launched*: Feb. 2014 14- *Cluster Size*: 5 members, 5 discovery proxies 15- *Order of Data Size*: 100s of Megabytes 16- *Operator*: CoreOS, brandon.philips@coreos.com 17- *Environment*: AWS 18- *Backups*: Periodic async to S3 19 20discovery.etcd.io is the longest continuously running etcd backed service that we know about. It is the basis of automatic cluster bootstrap and was launched in Feb. 2014: https://coreos.com/blog/etcd-0.3.0-released/. 21 22## OpenTable 23 24- *Application*: OpenTable internal service discovery and cluster configuration management 25- *Launched*: May 2014 26- *Cluster Size*: 3 members each in 6 independent clusters; approximately 50 nodes reading / writing 27- *Order of Data Size*: 10s of MB 28- *Operator*: OpenTable, Inc; sschlansker@opentable.com 29- *Environment*: AWS, VMWare 30- *Backups*: None, all data can be re-created if necessary. 31 32## cycoresys.com 33 34- *Application*: multiple 35- *Launched*: Jul. 2014 36- *Cluster Size*: 3 members, _n_ proxies 37- *Order of Data Size*: 100s of kilobytes 38- *Operator*: CyCore Systems, Inc, sys@cycoresys.com 39- *Environment*: Baremetal 40- *Backups*: Periodic sync to Ceph RadosGW and DigitalOcean VM 41 42CyCore Systems provides architecture and engineering for computing systems. This cluster provides microservices, virtual machines, databases, storage clusters to a number of clients. It is built on CoreOS machines, with each machine in the cluster running etcd as a peer or proxy. 43 44## Radius Intelligence 45 46- *Application*: multiple internal tools, Kubernetes clusters, bootstrappable system configs 47- *Launched*: June 2015 48- *Cluster Size*: 2 clusters of 5 and 3 members; approximately a dozen nodes read/write 49- *Order of Data Size*: 100s of kilobytes 50- *Operator*: Radius Intelligence; jcderr@radius.com 51- *Environment*: AWS, CoreOS, Kubernetes 52- *Backups*: None, all data can be recreated if necessary. 53 54Radius Intelligence uses Kubernetes running CoreOS to containerize and scale internal toolsets. Examples include running [JetBrains TeamCity][teamcity] and internal AWS security and cost reporting tools. etcd clusters back these clusters as well as provide some basic environment bootstrapping configuration keys. 55 56[teamcity]: https://www.jetbrains.com/teamcity/ 57