Service mesh is like an electric car—your friends talk about it, it’s hip, but you don’t have one yet. You’d probably rather wait and see how others manage it first. Nonetheless, it feels like the next tech evolution. Service mesh has garnered a bunch of attention in recent months—they help solve the many problems that arise after adopting a microservices architecture.
But is service mesh ready for all enterprises to utilize? It turns out its own proponents aren’t convinced this technology is 100% ready for broad adoption although it has many benefits, which include increased networking, observability and routing capabilities for microservices architectures.
We still have yet to see enough service mesh production use cases. And, each mesh framework is still maturing. Trade-offs to using a service mesh include increased latency, steep learning curves and an ongoing maintenance overhead. A lack of clear standardization for inter-mesh interoperability could be another concern (SMI was a proposed format, but now the industry seems more motivated behind Envoy’s xDS API).
All this is not to say it won’t be a pivotal part of a company’s future infrastructure or that it won’t offer helpful capabilities for the use cases that require it. Simply put, service mesh is a burgeoning field.
Read more at:
/Service Ventures Team
Opmerkingen