Category: Data, Infrastructure

Both the Meshery and Service Mesh Performance (SMP) projects joined the Cloud Native Computing Foundation (CNCF) earlier this month at the Sandbox level. For the TOC, what was enticing about that particular consideration is, this would mean the CNCF would then have a would then have a project that says, ‘Here is what makes a service mesh,’ and then here’s the thing that verifies that, in fact, it is a certain kind of a service mesh,” said Calcote. So all in one project, it’s defining things that are service meshes, validating that, in fact, they adhere to these specifications that they are what they say they are, and then Meshery does more on top of that, in terms of helping people get run service mesh successfully.”

While the SMI works to define the broadest characteristics that could apply to something defined as a service mesh, looking for the lowest common denominator, Meshery works in the opposite direction, trying to accentuate the differences and strengths of the individual services meshes.

It’s a multi-mesh world, that Meshery and SMI approach slightly differently, in so much as Meshery has 10 different adapters for 10 different service meshes, and it does so to allow each individual service mesh to expose its differentiated value, while SMI’s approach to that same goal is to provide a unified set of abstractions, a unified set of APIs,” explained Calcote.

Related Articles