Operating Consul at Scale
summary
35,000 bare‑metal hosts across 8 data centers run Consul for service discovery with ~3,000 service types and ~250,000 instances serving ~2.5M requests/sec. Registration is fully automated with automated Chef registration and ACLs lock down who can publish services. Operations use blackbox monitoring via Consul, per-service metrics like changes/sec and a timeline of events, plus Ruby tooling and a static UI built from Consul Template. A custom Consul fork lets the team deploy patches under two hours to fix production quickly.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:18Our 30 minutes presentation
- 0:54The discovery team
- 4:301/3) Full automation -as predictable as possible
- 10:36Logs, Info and History
- 11:23Ready to patch
- 12:30Work on upstream
- 17:12Consul-Templaterb: script everything! 1/2
- 19:14Useful configurations hints
- 21:05Benefits (1/2)
- 24:15Open-Source Tools
related talks
17mBuilding Robust Systems With Consul- 17mBuilding Robust Systems With Consul
57mService discovery as a modern [approach]
53mConsul Demystified: Exploring the principles behind better service discovery
54mUsing Terraform and Consul to delegate service deployment to service teams
32mService Mesh - Beyond the Hype
40mIntroducing A New Architecture for Simplified Service Mesh Deployments
27mConsul Mesh Federation Deep Dive