Program Speakers: Denis Jannot, Director of Field Engineering @Solo.io
The exploration of service mesh for any organization comes with some serious questions, including:
* What data plane should I use?
* How does this tie in with my existing API infrastructure?
* What kind of overhead do sidecar proxies demand?
As I’ve seen in my work with various organizations over the years “if you have a successful microservices deployment, then you have a service mesh whether it’s explicitly optimized as one or not.”
In this talk, we seek to understand the role of the data plane and how to pick the right component for the problem context. We start off by establishing the spectrum of data-plane components from shared gateways to in-code libraries with service proxies being along that spectrum. We clearly identify which scenarios would benefit from which part of the data-plane spectrum, show how modern service meshes including Istio, Linkerd, and Consul enable these optimizations and open source tools that extend them.