Cloud Native Communication: Using Ambassador and Consul Connect with Java Apps
summary
Overview of integrating Ambassador API gateway and Consul Connect service mesh with Java apps, using Envoy sidecars on Kubernetes, tradeoffs, and real production lessons (including 3 a.m. incidents). Covers ingress vs east‑west routing, mutual TLS, circuit breaking, canary routing, Helm/CRD configs, and an example GKE/Terraform migration with Spring Boot. Explains when to prefer a Java in‑process client vs sidecar, operational costs of installing meshes, and practical “vulcanization” adoption patterns and pitfalls.
AI-written summary · about
chapters (6)
- 0:00Introduction and talk overview
- 10:11API gateway fundamentals and ingress
- 20:47Service mesh concepts and trade-offs
- 35:15Decision points and implementation options
- 45:11Lessons learned and organizational impact
- 51:12Conclusion and key takeaways
related talks
36mUsing Ambassador to Build Cloud-Native Applications
38mModern Service Networking With Consul Connect, Envoy and Kubernetes
13mLightning Talk - Connecting and Migrating Heterogeneous Applications with Consul Servi...
59mCloud native, service-meshed Java Enterprise with Istio
22mConnectivity rules everything around us
56mCloud Native Java
01h 01mCloud Native Java
48mCloud Native Java
