Weaving Through the Mesh: Making Sense of Istio and Overlapping Technologies
summary
Replatforms an existing Spring Cloud + Eureka + gateway app onto Kubernetes, removes Eureka and shifts discovery, load‑balancing and circuit breaking into Istio sidecar injection, keeps an auth gateway, and implements routing with Istio CRDs (Gateway, VirtualService, DestinationRule) while discovering that callbacks for circuit breakers still require in‑app code and 30% delayed routing is trivial to express in VirtualService; also prototypes an RSocket broker cluster (ports 7002/8002, ping/pong) showing big bandwidth and latency savings but broker routing is early stage; API management remains useful at the edge for governance and billing.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:50Distributed systems: the new normal
- 2:53Challenges
- 7:08Solution implementation options
- 10:09Advantages
- 14:35Service mesh solutions
- 16:48Config
- 20:05Disable Eureka integrations for all apps
- 22:47Circuit Breakers & Fallbacks
- 25:57Retro (developer experience)
- 30:42RSocket vs HTTP - Key Differences
- 33:20RSocket Protocol Support
- 36:25RSocket Routing Broker
- 40:54On Kes: app to cluster communication
- 44:00Takeaways...
related talks
37mDistributed applications and Kubernetes: Frameworks or service meshes or both
01h 01mMeshing Around with Istio
25mIstio and why do we need it
25mApplication Networking on Kubernetes, where are we now?
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
21mIteratively Implementing Istio: Zero to Service Mesh with No Downtime
31mGetting a Handle on Your Microservices: Istio and the Open Source Broker API
52mEmpower Your Microservices with Istio Service Mesh