Project: etcd (Orchestration & Management / Coordination & Service Discovery)
File: ADOPTERS.md

title: Production users This 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 how etcd is working in the field and update this list. Application: https://kubernetes.io/ Environments: AWS, OpenStack, Azure, Google Cloud, Huawei Cloud, Bare Metal, etc This is a meta user; please feel free to document specific Kubernetes clusters! All Kubernetes clusters use etcd as their primary data store. This means etcd's users include such companies as , , , , and many many more. Application: https://github.com/coreos/discovery.etcd.io Launched: Feb. 2014 Cluster Size: 5 members, 5 discovery proxies Order of Data Size: 100s of Megabytes Operator: CoreOS, brandon.philips@coreos.com Environment: AWS Backups: Periodic async to S3 discovery.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/. Application: OpenTable internal service discovery and cluster configuration management Launched: May 2014 Cluster Size: 3 members each in 6 independent clusters; approximately 50 nodes reading / writing Order of Data Size: 10s of MB Operator: OpenTable, Inc; sschlansker@opentable.com Environment: AWS, VMWare Backups: None, all data can be re-created if necessary. Application: multiple Launched: Jul. 2014 Cluster Size: 3 members, n proxies Order of Data Size: 100s of kilobytes Operator: CyCore Systems, Inc, sys@cycoresys.com Environment: Baremetal Backups: Periodic sync to Ceph RadosGW and DigitalOcean VM CyCore 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. Application: multiple internal tools, Kubernetes clusters, bootstrappable system configs Launched: June 2015 Cluster Size: 2 clusters of 5 and 3 members; approximately a dozen nodes read/write Order of Data Size: 100s of kilobytes Operator: Radius Intelligence; jcderr@radius.com Environment: AWS, CoreOS, Kubernetes Backups: None, all data can be recreated if necessary. Radius Intelligence uses Kubernetes running CoreOS to containerize and scale internal toolsets. Examples include running and internal AWS security and cost reporting tools. etcd clusters back these clusters as well as provide some basic environment bootstrapping configuration keys. Application: kubernetes, vault backend, system configuration for microservices, scheduling, locks (future - service discovery) Launched: August 2015 Cluster Size: 2 clusters of 5 members in 2 DCs, n local proxies 1-to-1 with microservice, (ssl and SRV look up) Order of Data Size: kilobytes Operator: Vonage Environment: VMWare, AWS Backups: Daily snapshots on VMs. Backups done for upgrades. Application: embed etcd Launched: Mar 2016 Cluster Size: 3 or 5 members Order of Data Size: megabytes Operator: PingCAP, Inc. Environment: Bare Metal, AWS, etc. Backups: None. PD(Placement Driver) is the central controller in the TiDB cluster. It saves the cluster meta information, schedule the data, allocate the global unique timestamp for the distributed transaction, etc. It embeds etcd to supply high availability and auto failover. Application: System configuration for overlay network (Canal) Launched: June 2016 Cluster Size: 3 members for each cluster Order of Data Size: kilobytes Operator: Huawei Euler Department Environment: Backups: None, all data can be recreated if necessary. Application: system configuration for microservices, distributed locks Launched:

2016 Cluster Size: 3 members each with several clusters Order of Data Size: kilobytes Operator: Pandora, chenchao@qiniu.com Environment: Baremetal Backups: None, all data can be recreated if necessary Application: appcenter cluster for service discovery as backend. Launched: December 2016 Cluster Size: 1 cluster of 3 members per user. Order of Data Size: kilobytes Operator: Environment: QingCloud IaaS Backups: None, all data can be recreated if necessary. Application: system configuration for services, service discovery Launched: March 2016 Cluster Size: 3 clusters of 5 members Order of Data Size: several gigabytes Operator: Yandex; Environment: Bare Metal Backups: None Application: Meta data and configuration data for service discovery, Kubernetes, etc. Launched: Jan. 2015 Cluster Size: 3 members each with 10s of clusters Order of Data Size: 10s of Megabytes Operator: Tencent Game Operations Department Environment: Baremetal Backups: Periodic sync to backup server In Tencent games, we use Docker and Kubernetes to deploy and run our applications, and use etcd to save meta data for service discovery, Kubernetes, etc. Application: Kubernetes, distributed locks, etc. Launched: April 2016 Cluster Size: 1 cluster of 3 members Order of Data Size: 10s of MB Operator: Hyper.sh Environment: Baremetal Backups: None, all data can be recreated if necessary. In , the container service is backed by , a multi-tenant kubernetes distro. Moreover, we use etcd to coordinate the multiple manage services and store global meta data. Application: system configuration for services, service discovery, kubernetes in test environment Launched: October 2015 Cluster Size: 1 cluster of 3 members Order of Data Size: megabytes Operator: Meitu, hxj@meitu.com, Environment: Bare Metal Backups: None, all data can be recreated if necessary. Application: system configuration for services, service discovery Launched: June 2016 Cluster Size: 1 cluster of 7 members Order of Data Size: megabytes Operator: Grab, , Environment: AWS Backups: None, all data can be recreated if necessary. Application: container management Launched: Sep. 2015 Cluster Size: 1000+ deployments, each deployment contains a 3 node cluster. Order of Data Size: 100s of Megabytes Operator: daocloud.io Environment: Baremetal and virtual machines Backups: None, all data can be recreated if necessary. In , we use Docker and Swarm to deploy and run our applications, and we use etcd to save metadata for service discovery. Application: Kubernetes Launched: April 2016 Cluster Size: Multiple clusters, multiple sizes Order of Data Size: 100s of Megabytes Operator: branch.io Environment: AWS, Kubernetes Backups: EBS volume backups At , we use kubernetes heavily as our core microservice platform for staging and production. Application: SkyDNS, Kubernetes, UDC, CMDB and other distributed systems Launched: April 2016 Cluster Size: 3 clusters of 5 members Order of Data Size: several gigabytes Operator: Baidu Waimai Operations Department Environment: CentOS 6.5 Backups: backup scripts Application: Kubernetes Launched: Jan 2017 Cluster Size: Multiple clusters of 3 members Order of Data Size: 100s of Megabytes Operator: Salesforce.com (krmayankk@github) Environment: BareMetal Backups: None, all data can be recreated Application: Service discovery, locking, ephemeral application data Launched: January 2017 Cluster Size: 2 clusters of 7 members Order of Data Size: Megabytes Operator: Hosted Graphite (sre@hostedgraphite.com) Environment: Bare Metal Backups: None, all data is considered ephemeral. Application: Transwarp Data Cloud, Transwarp Operating System, Transwarp Data Hub, Sophon Launched: January 2016 Cluster Size: Multiple clusters, multiple sizes Order of Data Size: Megabytes Operator: Trasnwarp Operating System Environment: Bare Metal, Container Backups: backup scripts Application: cluster configuration management Launched: February 2023 Cluster Size: single cluster, 3 nodes Order of Data Size: kilobytes Operator: Cyberfusion Environment: Debian on VMs Backups: periodic `etcdctl snapshot save` + rotation in cron. More about our setup: https://cyberfusion.io/articles/building-hosting-infrastructure-in-2024-configuration-management-part-1