Summary: To service mash or not? That’s a good question! Not every architecture and project needs a service mesh but for running distributed microservices architectures service mashes provide a lot of essential features such as service discovery, traffic routing, security, observability ..<br><br>We invited Matt Turner (@mt165), CTO at Native Wave, to tell us all we need to know about service mashes. We get a deep dive into Istio, one of the most popular current service mashes, the architecture and how the individual components such as Envoy, Pilot, Mixer and Citadel work together. We also chat about the tradeoff between performance, latency, throughput and service mash capabilities. If you want to learn more make sure to check out Matt’s online content such as blogs and recorded conference presentations on <a href="https://mt165.co.uk/" rel="noopener">https://mt165.co.uk/</a>.<br><br>Native Wave<br> <a href="https://nativewave.io/" rel="noopener">https://nativewave.io/</a><br><br>Istio vs. Linkerd CPU Overhead Benchmarks by Michael Kipper<br> Initial Observations:<br> <a href="https://medium.com/" rel="noopener">https://medium.com/</a>@michael_87395/benchmarking-istio-linkerd-cpu-c36287e32781<br> Second Analysis: <br> <a href="https://medium.com/" rel="noopener">https://medium.com/</a>@michael_87395/benchmarking-istio-linkerd-cpu-at-scale-5f2cfc97c7fa
