Service mesh compare tool (istio and linkerd for example)
A service mesh is a dedicated infrastructure layer for making service-to-service communication safe, fast, and reliable. If you’re building a cloud native application, you need a service mesh.
Istio
Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio’s control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes.It was open-sourced in May 2017 by Google, IBM, and Lyft, and it has since gained a lot of mindshare.
Linkerd
has been around a bit longer, starting as a network proxy in version 1.0. It merged with a preexisting service mesh (Conduit) in September 2018 to form Linkerd 2.0, which adds service mesh features to the network proxy.
We create a tool (open source) that expose an infrastructure to compare service mesh tools in a lot of categories. We write the tool ui in vue.js and node . Service for sending network packet ( app bomb) written in Go.Ui that expose the graph to the user in the end.
Here is the main flow of the tool right now:
And a screenshot from the ui:
Main flow
In general the main flow is:
We have a Ui in vue.js that the user enter the relevant parameters. After it we have a node service that run it on the relevant cluster. In the specific scenario that we implemented for right now it call a go service that sending network requests to an application (like book info that mentioned in istio documentation ) . The ui have also option to show the relevant output form grafana graphs.
Goals for the future
- Add support for another service mesh tools .
- Add more features to Ui .
- Add more services (like we implemented in go) to compare another scenarios.
Link to our git hub repo : https://github.com/tikal-fuseday/service-mesh-fight
