Service mesh: promise or peril?

Click for: original source

An article by Richard Li about service meshes such as Istio, Linkerd, and Cilium which are gaining increased visibility as companies adopt microservice architectures. Richard Li is the CEO/co-founder of Datawire, which builds open source tools for developers on Kubernetes.

The arguments for a service mesh are compelling: full-stack observability, transparent security, systems resilience, and more. ** Microservices aren’t free – they introduce new failure modes.**

The three core strategies for managing failure in a microservices architecture are proactive testing, mitigation, and rapid response.

If you have a small number of microservices or a shallow topology, consider delaying adoption of a service mesh, and evaluate alternative strategies for failure management.

If you are deploying a service mesh, be prepared to invest ongoing effort in integrating the mesh into your software development lifecycle.

This and more information about how to adopt service mesh or what to consider before adopting in the article. Excellent read!

[Read More]

Tags serverless cloud microservices