Tide's Self-Service Service Mesh With Consul
summary
Tide replaces a brittle ALB mesh with Consul in about six weeks, rolling Consul HCP peered into the VPC, adding Envoy sidecars per ECS task, and populating upstreams via service manifests so services see local ports. Intentions live in a single git repo for peer-reviewed allow rules, ingress works through an ingress gateway fronted by ALB, and a developer-local Envoy joins a mesh. Cutover shows no downtime as ALB traffic drops to zero.
AI-written summary · about
chapters (9)
- 0:00Introduction to Tide
- 1:23Need for a service mesh
- 7:05Designing the architecture
- 8:25Implementation details
- 10:54Configuration and deployment
- 14:34Managing service intentions
- 17:25API gateway integration
- 19:28Developer ingress strategy
- 21:55Migration and rollout plan
related talks
54mUsing Terraform and Consul to delegate service deployment to service teams
40mBuilding a Modern Infrastructure Stack
29mService Discovery on Lattice with Consul
46mProgressive Deployments with Consul Service Mesh
01h 11mCrack the monolith with Consul and Nomad
19mPlanning the Zero-Downtime Lifecycle of Your Service Mesh
39mAPI Gateway to Service Mesh: Navigating a Changing Landscape
24mA10 & HashiCorp Network Infrastructure Automation with Consul-Terraform-Sync