Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Istio

951
1.5K
+ 1
54
Maesh

1
7
+ 1
0
Add tool
Decisions about Istio and Maesh
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 315.5K views

Istio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn-keyIstio based on powerful Envoy whereas Kong based on Nginx. Istio is K8S native as well it's actively developed when k8s was successfully accepted with production-ready apps whereas Kong slowly migrated to start leveraging K8s. Istio has an inbuilt turn key solution with Rancher whereas Kong completely lacks here. Traffic distribution in Istio can be done via canary, a/b, shadowing, HTTP headers, ACL, whitelist whereas in Kong it's limited to canary, ACL, blue-green, proxy caching. Istio has amazing community support which is visible via Github stars or releases when comparing both.

See more
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of Istio
Pros of Maesh
  • 14
    Zero code for logging and monitoring
  • 9
    Service Mesh
  • 8
    Great flexibility
  • 5
    Resiliency
  • 5
    Powerful authorization mechanisms
  • 5
    Ingress controller
  • 4
    Easy integration with Kubernetes and Docker
  • 4
    Full Security
    Be the first to leave a pro

    Sign up to add or upvote prosMake informed product decisions

    Cons of Istio
    Cons of Maesh
    • 17
      Performance
      Be the first to leave a con

      Sign up to add or upvote consMake informed product decisions

      566
      2.7K
      521
      - No public GitHub repository available -

      What is 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, Mesos, etc.

      What is Maesh?

      It 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.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use Istio?
      What companies use Maesh?
        No companies found
        Manage your open source components, licenses, and vulnerabilities
        Learn More

        Sign up to get full access to all the companiesMake informed product decisions

        What tools integrate with Istio?
        What tools integrate with Maesh?

        Sign up to get full access to all the tool integrationsMake informed product decisions

        What are some alternatives to Istio and Maesh?
        linkerd
        linkerd is an out-of-process network stack for microservices. It functions as a transparent RPC proxy, handling everything needed to make inter-service RPC safe and sane--including load-balancing, service discovery, instrumentation, and routing.
        Envoy
        Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
        Kubernetes
        Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
        Conduit
        Conduit is a lightweight open source service mesh designed for performance, power, and ease of use when running applications on Kubernetes. Conduit is incredibly fast, lightweight, fundamentally secure, and easy to get started with.
        Kong
        Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform.
        See all alternatives