Best Service Mesh for Meshery

Connect, secure, control, and observe services. Istio’s traffic routing rules let you easily control the flow of traffic and API calls between services. Istio simplifies configuration of service-level properties like circuit breakers, timeouts, and retries, and makes it easy to set up important tasks like A/B testing, canary rollouts, and staged rollouts with percentage-based traffic splits. It also provides out-of-box failure recovery features that help make your application more robust against failures of dependent services or the network. Istio Security provides a comprehensive security solution to solve these issues. This page gives an overview on how you can use Istio security features to secure your services, wherever you run them. In particular, Istio security mitigates both insider and external threats against your data, endpoints, communication, and platform. Istio generates detailed telemetry for all service communications within a mesh.

The always-free NGINX Service Mesh scales from open source projects to a fully supported, secure, and scalable enterprise‑grade solution. Take control of Kubernetes with NGINX Service Mesh, featuring a unified data plane for ingress and egress management in a single configuration. The real star of NGINX Service Mesh is the fully integrated, high-performance data plane. Leveraging the power of NGINX Plus to operate highly available and scalable containerized environments, our data plane brings a level of enterprise traffic management, performance, and scalability to the market that no other sidecars can offer. It provides the seamless and transparent load balancing, reverse proxy, traffic routing, identity, and encryption features needed for production-grade service mesh deployments. When paired with the NGINX Plus-based version of NGINX Ingress Controller, it provides a unified data plane that can be managed with a single configuration.

A common flat vL3 domain allowing DBs running in multiple clusters/clouds/hybrid to communicate just with each other for DB replication. Workloads from multiple companies connecting to a single ‘collaborative’ Service Mesh for cross company interactions. Each workload has a single option of what connectivity domain to be connected to, and only workloads in a given runtime domain could be part of its connectivity domain. In short: Connectivity Domains are Strongly Coupled to Runtime Domains. A central tenant of Cloud Native is Loose Coupling. In a Loosely Coupled system, the ability for each workload to receive service from alternative providers is preserved. What Runtime Domain a workload is running in is a non-sequitur to its communications needs. Workloads that are part of the same App need Connectivity between each other no matter where they are running.

A multi-cloud service networking platform to connect and secure services across any runtime platform and public or private cloud. Real-time health and location information of all services. Progressive delivery and zero trust security with less overhead. Receive peace of mind that all HCP connections are secured out of the box. Gain insight into service health and performance metrics with built-in visualization directly in the Consul UI or by exporting metrics to a third-party solution. Many modern applications have migrated towards decentralized architectures as opposed to traditional monolithic architectures. This is especially true with microservices. Since applications are composed of many inter-dependent services, there's a need to have a topological view of the services and their dependencies. Furthermore, there is a desire to have insight into health and performance metrics for the different services.

Traefik Mesh is a straight-forward, easy to configure, and non-invasive service mesh that allows visibility and management of the traffic flows inside any Kubernetes cluster. By improving monitoring, logging, and visibility, as well as implementing access controls. Allows administrators to increase the security of their clusters easily and quickly. By being able to monitor and trace how applications communicate in your Kubernetes cluster, administrators are able to optimize internal communications, and improve application performance. Reducing the time to learn, install, and configure makes it easier to implement, and to provide value for the time actually spent implementing. Administrators can focus on their business applications. Being open source means that there is no vendor lock-in, as Traefik Mesh is opt-in by design.

The open-source control plane for service mesh, delivering security, observability, routing and more. Built on top of Envoy, Kuma is a modern control plane for Microservices & Service Mesh for both K8s and VMs, with support for multiple meshes in one cluster. Out of the box L4 + L7 policy architecture to enable zero trust security, observability, discovery, routing and traffic reliability in one click. Getting up and running with Kuma only requires three easy steps. Natively embedded with Envoy proxy, Kuma Delivers easy to use policies that can secure, observe, connect, route and enhance service connectivity for every application and services, databases included. Build modern service and application connectivity across every platform, cloud and architecture. Kuma supports modern Kubernetes environments and Virtual Machine workloads in the same cluster, with native multi-cloud and multi-cluster connectivity to support the entire organization.

Linkerd adds critical security, observability, and reliability features to your Kubernetes stack—no code change required. Linkerd is 100% Apache-licensed, with an incredibly fast-growing, active, and friendly community. Built in Rust, Linkerd's data plane proxies are incredibly small (<10 mb) and blazing fast (p99 < 1ms). No complex APIs or configuration. For most applications, Linkerd will “just work” out of the box. Linkerd's control plane installs into a single namespace, and services can be safely added to the mesh, one at a time. Get a comprehensive suite of diagnostic tools, including automatic service dependency maps and live traffic samples. Best-in-class observability allows you to monitor golden metrics—success rate, request volume, and latency—for every service.