Istio Platform vs Spring and MicroProfile frameworks
summary
Compares Istio sidecar Envoy vs Spring Netflix OSS and MicroProfile by showing where platform policies clash with in-app decisions: Kubernetes DNS or Eureka service discovery, YAML virtual services overriding client choice, mutual TLS and JWT validation in Istio, and Envoy fault injection. Demonstrates the retry multiplication problem (3 app retries × 3 Istio retries = 9 attempts), shows where fallbacks still require app code, and recommends choosing either platform or framework for circuit breaking, retries and identity propagation.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:47Outline
- 3:59Everyone's doing microservices...
- 4:47Microservice reality...
- 5:17New patterns for old problems
- 7:36Framework support - Micro Profile
- 9:00Framework support - Issues
- 18:11Service Discovery - Combined
- 24:59Fault tolerance - Combined
- 28:55Security
- 35:46Trace, logging, metrics
- 38:52Summary
related talks
40mIstio, your K8S cluster best friend
48mIstio An open platform to connect, manage, and secure microservices
49mMaking Microservices Micro with Istio Service Mesh
36mIstio to the rescue
01h 01mIstio Service Mesh & pragmatic microservices architecture
55mEmpower Your Microservices with Istio Service Mesh
51mService Mesh with Istio and MicroProfile — A Harmonious Combination?
50mMaking Microservices Micro with Istio & Kubernetes