SMI is an open project that Microsoft has been developing in recent months. Through that early stage, the company has already acquired major partners such as VMWare, Weaveworks, Pivotal, Docker, AspenMesh, and more. Service Mesh has brought majors changes to networks through Kubernetes. Previously, networks were limited but Service Mesh allows smarter integration through management APIs. The technology has become increasingly popular with developers. “There’s extensibility just all over the system,” Brendan Burns, Kubernetes cofounder and Microsoft distinguished engineer, told VentureBeat. “And service mesh stood out as this place where there wasn’t any accessibility and there wasn’t any generic interface. It wasn’t following the pattern of the way that the rest of the Kubernetes architecture had been designed, or had been retrofitted, in all honesty.”
Universal Interface
Microsoft’s Service Mesh Interface is a universal API interface that allows developers to leverage mesh services without being linked to a specific tool. SMI specification gathers common APIs to give developers the freedom to create their own implementations. “Some of the people who we’re partnering with are excited because they’re not going to build a service mesh but they want to build tooling that targets a service mesh,” Burns explained. “Maybe it’s a better way of doing experiments, or rollouts of software. And if they have to choose a particular service mesh’s API, that tool has less reach. We’re in the business of making generic infrastructure, and different customers will make different choices. Someone might choose to use Consul by HashiCorp, someone might choose Istio.” SMI specs offer three service mesh tools, Policy, Telemetry, and Management:
