Service mesh across hybrid infrastructure
summary
Walks through configuring AWS Cloud Map and HashiCorp Consul to register services bidirectionally, using a consul-aws sync binary and Route 53 so AWS services resolve on-prem and vice versa; deploys two Consul control planes to “stretch” the mesh, pushes Envoy-based sidecars (proxies on localhost:1992), and exercises canary and A/B splits (attempted 50/50 cutover that shows intermittent failures, toggled back and fixed). Demonstrates request tracing from an AWS app to an on‑prem Postgres, proves visibility and gradual migration control, and notes eventual plan to retire the mesh while keeping service discovery sync.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 0:53Challenges in hybrid infrastructure
- 2:20Why wont X connect
- 7:27How to build in sight
- 9:53Overview
- 10:30Service mesh
- 12:07Premise
- 13:00Migration to AWS
- 13:50Demo
- 16:50Recap
- 17:23Stretching the mesh
- 18:55Mitigation
- 21:50Troubleshooting
- 22:35Fixing API on AWS
- 24:40Evaluating refactorings
- 25:35Getting rid of service mesh
- 26:25Service Discovery Service
- 28:40Testing
- 29:40Web client
- 32:30Configure Proxy
- 33:50Final diagram
- 35:05Summary
- 36:45Resources
- 37:40Questions
- 39:10Mesh gateways
- 40:20Mesh template
- 42:00Mesh vs Console
- 43:10Best practice
- 45:10Multiple instances of same API
- 45:40Load balancer
- 46:30API Gateway
- 48:10Connect Configuration
- 49:20Overhead
- 50:03What to do in the case of sync break down
- 51:20Service mesh for legacy applications
related talks
22mConsul Roadmap
47mService mesh options with Istio, Linkerd, and/or Consul
26mNavigating the Service Mesh Landscape - Paul Bouwer, Microsoft
43mService Mesh and the future of networking
38mPanel Discussion: Ask Us Anything: Microservices and Service Mesh
23mBridging the gap between on-prem and cloud: a story about...
33mTake Envoy Beyond a K8s Service Mesh - to Legacy Bare Metal & VMs + More
28mDeploying hybrid topologies with k8s & Envoy: a look at service discovery