Service Meshes: Istio, Linkerd - or No Mesh at All?
You need to be signed in to add a collection
Service meshes like Istio and Linkerd 2 solve many problems of current microservice applications. They add observability, routing, resilience, and security features as a dedicated infrastructure layer. Communication between applications can be monitored, configured and secured without adding or changing application code. Sounds too good to be true? Indeed, a service mesh does not come without a price: mental complexity, increased resource consumption, and latency being the main challenges. We will talk about meaningful use cases for service meshes, drawbacks, and differences between the various implementations. **Attendees:** <a href="https://gotopiachicago2021.slack.com/archives/C01U6LMG9K8" target="_blank">Join the #devops channel on Slack to send your questions to Eberhard and Hanna</a>
Transcript
Service meshes like Istio and Linkerd 2 solve many problems of current microservice applications. They add observability, routing, resilience, and security features as a dedicated infrastructure layer. Communication between applications can be monitored, configured and secured without adding or changing application code.
Sounds too good to be true? Indeed, a service mesh does not come without a price: mental complexity, increased resource consumption, and latency being the main challenges. We will talk about meaningful use cases for service meshes, drawbacks, and differences between the various implementations.
Attendees: Join the #devops channel on Slack to send your questions to Eberhard and Hanna
About the speakers
Consultant at InnoQ
Prolific author of "Microservices: Flexible Software Architecture". Working for 15+ years as an architect & consultant