The State of the Service Mesh, Part 2: Availability


In the world of microservices, the pace of change is unyielding but the excitement is surely building, as a critical mass of industry thought leaders and practitioners are moving beyond mere theory and talk. Early‑adopter organizations that have workloads requiring service mesh functionality now want to prove its viability as a production‑ready architecture by implementing actual solutions for some compelling “low hanging fruit” use cases.

This post is the second installment in our series on service mesh:

In this post, we return to highlight one of the service mesh capabilities that we identified as core to the service mesh value proposition: availability. In Part 1, we put a spotlight on how I&O and DevOps leaders are responsible for deploying mission‑critical apps with a delivery infrastructure, including service meshes, that delivers fault tolerance. The control plane is where most of the innovation is happening, as the data‑plane infrastructure available with tools like NGINX and Envoy is already enterprise‑grade. The exciting news is that vendors have been developing their control planes quickly and have largely addressed some of the early concerns about the control plane as a potential single point of failure.

Following is a roundup of some of the recent innovations and developments for highly available control plane at the heart of a maturing, commercially supported service mesh:

One thing for certain is that the speed of change in the service mesh space is not slowing down. Vendors are racing to develop highly available service mesh control planes and although several models are now available, no single solution yet emerged as dominant. We live in a dynamic and exciting world of microservices. Watch for the next post on the topic of how security is addressed in the service mesh space. Until then, enjoy the ride.

Retrieved by Nick Shadrin from website.