“It’s not just me saying this. We see the data in the [Azure Kubernetes Service] support queue of customers who are trying to use this stuff — and they’re struggling right here. This is just hard technology to use — hard technology to build at scale,” he added.
Until now Microsoft had set itself out as a neutral party in the service mesh battle, offering Azure customers a Service Mesh Interface that supported various options, including popular open source options such as Istio, Linkerd and Consul, as well as Amazon Web Services’ own App Mesh.
Now, according to Microsoft, OSM is intended to be as lightweight an option as possible. It runs on Kubernetes, and the data plane element is based on the popular Envoy proxy, all configured with service mesh interface APIs. Long story short? “OSM injects an Envoy proxy as a sidecar container next to each instance of …