Service Mesh Interface (SMI) is a specification for service meshes that run on Kubernetes. SMI defines a common standard that can be implemented by a variety of service mesh projects and vendors.
SMI’s aim for consistent APIs facilitates Meshery’s same goals, allowing for users and tools to flourish. As SMI was unveiled at KubeCon + CloudNativeCon Europe 2019, so did Meshery’s compatibility. Layer5 is pleased to partner with Microsoft in support of SMI.
To read more about it, please checkout out the announcement blog post here.
The Benchmark Specification is a
common format for describing and capturing performance benchmark tests and results. This specification is
currently being advanced through discussion in the Meshery project.
Why create Meshery and not use regpatrol?
regpatrol is not open source or available in binary form to use.
What are some differences between regpatrol and Meshery?
Telemetry - regpatrol sources telemetry from Mixer Prometheus adapter and uses IBM's proprietary node agent.
Meshery sources from Mixer Prometheus adapter and uses Prometheus node-exporter.
Traffic type - regpatrol uses jmeter, which can parse responses and perform functional tests.
Meshery is using fortio, which is for load-gen and perf-testing only.
Why use Meshery?
because its an open source, vendor neutral projects that facilitates testing across meshes.
because fortio is not packaged into a mesh testing utility, but is only a load-generator unto its own.
because regpatrol is closed sourcej, binary is not released, scripted for one mesh, and is produced by a vendor of that mesh.