Service Discovery on Lattice with Consul
summary
Shows how Lattice (Diego scheduler, Docker containers) uses Consul for service discovery by registering MySQL services in Consul and demonstrating failover when one of two masters goes down. Explains Consul’s DNS and HTTP APIs, script and TTL health checks, and Raft-based quorum (recommendation: 3 or 5 Consul servers for quorum). Presents an end-to-end setup on Lattice, details actual health-check mechanics and how Consul reroutes clients to healthy hosts.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:30Introduction
- 4:05Main Features for Lattice
- 5:36Dynamic Routing
- 10:05Console Agent
- 11:05Service Discovery
- 11:48Health Checking for Failure Detection
- 15:44Problems with Service Discovery
related talks
17mBuilding Robust Systems With Consul
53mConsul Demystified: Exploring the principles behind better service discovery
57mService discovery as a modern [approach]
17mBuilding Robust Systems With Consul
54mUsing Terraform and Consul to delegate service deployment to service teams
28mOperating Consul at Scale
01h 25mLattice: A Cloud-Native Platform for Your Spring Applications
02mLuis Bosque at WeCode Fest 2018
