Fault Tolerance: Microservice Chassis vs. Service Mesh
summary
Compares fault-tolerance provided by service meshes (Linkerd) versus microservice chassis frameworks (Spring Boot, MicroProfile) using Java. Explains differences, advantages and disadvantages of each approach and shows how to correctly implement Retry, Timeout and related fault‑tolerance patterns in distributed systems.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:06Microservices fault tolerance
- 2:33Cloud-native evolution
- 4:39Chassis vs service mesh
- 7:52Fault-tolerance patterns
- 10:20Coding drawbacks
- 11:02Service Mesh capabilities
- 12:51Service Mesh interceptor
- 14:57Demo architecture
- 16:44Kubernetes deployment
- 21:00Service failure behavior
- 23:24Microservice Chassis Java
- 25:13Oracle Cloud deployment
- 27:21Initial service test
- 28:45Cascading failures
- 31:20Linkerd installation
- 32:27Linkerd instrumentation
- 34:13Observability metrics
- 35:16Retry configuration
- 36:43Fault tolerance results
- 37:26Summary
- 37:46Q&A
related talks
56mService Meshes - Powering the next wave of microservice architectures
43mWTF Do We Need a Service Mesh?
37mPanel Discussion: Ask Us Anything: Microservices and Service Mesh
40mComparison of Current Service Mesh Architectures
35mNavigating the Service Mesh Ecosystem
37mDistributed applications and Kubernetes: Frameworks or service meshes or both
11mWelcome & Opening Remarks
47mService-Mesh: an In-Depth View of Technologies and Reasons for Adoption