Building Robust Systems With Consul
summary
Consul provides service discovery via DNS and HTTP API, uses a per-server agent that caches and serves stale data, and exposes a KV store with dynamic changes plus simple Nagios-style health checks; DNS covers about 95% of cases, health checks run every five seconds, and config changes propagate in milliseconds. Multi‑datacenter queries and leader‑election make metadata and keys highly available, and the demo wiring shows existing apps working without code changes.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:45Answering Questions
- 5:20Locality
- 6:15Service Discovery
- 7:20DNS
- 12:40Configuration Console
- 14:15Console DNS
- 14:57Health Checks
related talks
17mBuilding Robust Systems With Consul
28mOperating Consul at Scale
53mConsul Demystified: Exploring the principles behind better service discovery
29mService Discovery on Lattice with Consul
57mService discovery as a modern [approach]
54mUsing Terraform and Consul to delegate service deployment to service teams
01h 11mCrack the monolith with Consul and Nomad
02mLuis Bosque at WeCode Fest 2018