Alternatives to Istio logo

Alternatives to Istio

linkerd, Envoy, Kubernetes, Conduit, and Kong are the most popular alternatives and competitors to Istio.
597
1.1K
+ 1
42

What is Istio and what are its top alternatives?

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.
Istio is a tool in the Microservices Tools category of a tech stack.
Istio is an open source tool with 27.2K GitHub stars and 5.4K GitHub forks. Here’s a link to Istio's open source repository on GitHub

Top Alternatives to Istio

  • linkerd

    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

    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

    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

    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

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

  • AWS App Mesh

    AWS App Mesh

    AWS App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and control containerized microservices. App Mesh standardizes how your microservices communicate, giving you end-to-end visibility and helping to ensure high-availability for your applications. App Mesh gives you consistent visibility and network traffic controls for every microservice in an application. You can use App Mesh with Amazon ECS (using the Amazon EC2 launch type), Amazon EKS, and Kubernetes on AWS. ...

  • Apigee

    Apigee

    API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world. ...

  • Consul

    Consul

    Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable. ...

Istio alternatives & related posts

linkerd logo

linkerd

87
222
7
Twitter-Style Operability for Microservices
87
222
+ 1
7
PROS OF LINKERD
  • 3
    CNCF Project
  • 1
    Fast Integration
  • 1
    Pre-check permissions
  • 1
    Light Weight
  • 1
    Service Mesh
CONS OF LINKERD
    Be the first to leave a con

    related linkerd posts

    Envoy logo

    Envoy

    213
    383
    8
    C++ front/service proxy
    213
    383
    + 1
    8
    PROS OF ENVOY
    • 8
      GRPC-Web
    CONS OF ENVOY
      Be the first to leave a con

      related Envoy posts

      Joseph Irving
      DevOps Engineer at uSwitch · | 7 upvotes · 106.8K views
      Shared insights
      on
      Kubernetes
      Envoy
      Go
      at

      At uSwitch we wanted a way to load balance between our multiple Kubernetes clusters in AWS to give us added redundancy. We already had ingresses defined for all our applications so we wanted to build on top of that, instead of creating a new system that would require our various teams to change code/config etc.

      Envoy seemed to tick a lot of boxes:

      • Loadbalancing capabilities right out of the box: health checks, circuit breaking, retries etc.
      • Tracing and prometheus metrics support
      • Lightweight
      • Good community support

      This was all good but what really sold us was the api that supported dynamic configuration. This would allow us to dynamically configure envoy to route to ingresses and clusters as they were created or destroyed.

      To do this we built a tool called Yggdrasil using their Go sdk. Yggdrasil effectively just creates envoy configuration from Kubernetes ingress objects, so you point Yggdrasil at your kube clusters, it generates config from the ingresses and then envoy can loadbalance between your clusters for you. This is all done dynamically so as soon as new ingress is created the envoy nodes get updated with the new config. Importantly this all worked with what we already had, no need to create new config for every application, we just put this on top of it.

      See more
      Shared insights
      on
      Envoy
      HAProxy
      Traefik
      NGINX

      We are looking to configure a load balancer with some admin UI. We are currently struggling to decide between NGINX, Traefik, HAProxy, and Envoy. We will use a load balancer in a containerized environment and the load balancer should flexible and easy to reload without changes in case containers are scaled up.

      See more
      Kubernetes logo

      Kubernetes

      33.8K
      28.3K
      601
      Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
      33.8K
      28.3K
      + 1
      601
      PROS OF KUBERNETES
      • 152
        Leading docker container management solution
      • 121
        Simple and powerful
      • 96
        Open source
      • 73
        Backed by google
      • 56
        The right abstractions
      • 24
        Scale services
      • 17
        Replication controller
      • 9
        Permission managment
      • 6
        Simple
      • 5
        Supports autoscaling
      • 5
        Cheap
      • 3
        Reliable
      • 3
        No cloud platform lock-in
      • 3
        Self-healing
      • 3
        Open, powerful, stable
      • 3
        Scalable
      • 3
        Promotes modern/good infrascture practice
      • 2
        Cloud Agnostic
      • 2
        Backed by Red Hat
      • 2
        Custom and extensibility
      • 2
        Quick cloud setup
      • 2
        Captain of Container Ship
      • 2
        A self healing environment with rich metadata
      • 1
        Everything of CaaS
      • 1
        Easy setup
      • 1
        Expandable
      • 1
        Runs on azure
      • 1
        Sfg
      • 1
        Golang
      • 1
        Gke
      CONS OF KUBERNETES
      • 13
        Poor workflow for development
      • 11
        Steep learning curve
      • 5
        Orchestrates only infrastructure
      • 2
        High resource requirements for on-prem clusters

      related Kubernetes posts

      Conor Myhrvold
      Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 3.7M views

      How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

      Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

      Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

      https://eng.uber.com/distributed-tracing/

      (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

      Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

      See more
      Yshay Yaacobi

      Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

      Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

      After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

      See more
      Conduit logo

      Conduit

      5
      17
      0
      Open-source service mesh for Kubernetes
      5
      17
      + 1
      0
      PROS OF CONDUIT
        Be the first to leave a pro
        CONS OF CONDUIT
          Be the first to leave a con

          related Conduit posts

          Kong logo

          Kong

          428
          1K
          127
          Open Source Microservice & API Management Layer
          428
          1K
          + 1
          127
          PROS OF KONG
          • 36
            Easy to maintain
          • 30
            Easy to install
          • 22
            Flexible
          • 20
            Great performance
          • 5
            Api blueprint
          • 4
            Custom Plugins
          • 3
            Kubernetes-native
          • 2
            Agnostic
          • 1
            12312312
          • 1
            123123
          • 1
            1
          • 1
            123
          • 1
            Documentation is clear
          • 0
            12
          CONS OF KONG
            Be the first to leave a con

            related Kong posts

            Al Tsang
            Problem/Challenge

            We needed a lightweight and completely customizable #microservices #gateway to be able to generate #JWT and introspect #OAuth2 tokens as well. The #gateway was going to front all #APIs for our single page web app as well as externalized #APIs for our partners.

            Contenders

            We looked at Tyk Cloud and Kong. Kong's plugins are all Lua based and its core is NGINX and OpenResty. Although it's open source, it's not the greatest platform to be able to customize. On top of that enterprise features are paid and expensive. Tyk is Go and the nomenclature used within Tyk like "sessions" was bizarre, and again enterprise features were paid.

            Decision

            We ultimately decided to roll our own using ExpressJS into Express Gateway because the use case for using ExpressJS as an #API #gateway was tried and true, in fact - all the enterprise features that the other two charge for #OAuth2 introspection etc were freely available within ExpressJS middleware.

            Outcome

            We opened source Express Gateway with a core set of plugins and the community started writing their own and could quickly do so by rolling lots of ExpressJS middleware into Express Gateway

            See more
            Anas MOKDAD
            Shared insights
            on
            Kong
            Istio

            As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

            See more
            AWS App Mesh logo

            AWS App Mesh

            19
            158
            0
            Easily monitor and control microservices running on AWS
            19
            158
            + 1
            0
            PROS OF AWS APP MESH
              Be the first to leave a pro
              CONS OF AWS APP MESH
                Be the first to leave a con

                related AWS App Mesh posts

                Apigee logo

                Apigee

                172
                480
                26
                Intelligent and complete API platform
                172
                480
                + 1
                26
                PROS OF APIGEE
                • 10
                  Highly scalable and secure API Management Platform
                • 5
                  Quick jumpstart
                • 5
                  Good documentation
                • 3
                  Fast and adjustable caching
                • 3
                  Easy to use
                CONS OF APIGEE
                • 6
                  Expensive

                related Apigee posts

                A Luthra
                VP Software Engrg at Reliant · | 2 upvotes · 292.7K views
                Shared insights
                on
                Apigee
                Amazon API Gateway

                Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

                See more
                Consul logo

                Consul

                979
                1.2K
                203
                A tool for service discovery, monitoring and configuration
                979
                1.2K
                + 1
                203
                PROS OF CONSUL
                • 59
                  Great service discovery infrastructure
                • 35
                  Health checking
                • 27
                  Distributed key-value store
                • 25
                  Monitoring
                • 23
                  High-availability
                • 11
                  Web-UI
                • 10
                  Token-based acls
                • 6
                  Gossip clustering
                • 5
                  Dns server
                • 1
                  Docker integration
                • 1
                  Not Java
                CONS OF CONSUL
                  Be the first to leave a con

                  related Consul posts

                  John Kodumal

                  As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

                  We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

                  See more

                  Since the beginning, Cal Henderson has been the CTO of Slack. Earlier this year, he commented on a Quora question summarizing their current stack.

                  Apps
                  • Web: a mix of JavaScript/ES6 and React.
                  • Desktop: And Electron to ship it as a desktop application.
                  • Android: a mix of Java and Kotlin.
                  • iOS: written in a mix of Objective C and Swift.
                  Backend
                  • The core application and the API written in PHP/Hack that runs on HHVM.
                  • The data is stored in MySQL using Vitess.
                  • Caching is done using Memcached and MCRouter.
                  • The search service takes help from SolrCloud, with various Java services.
                  • The messaging system uses WebSockets with many services in Java and Go.
                  • Load balancing is done using HAproxy with Consul for configuration.
                  • Most services talk to each other over gRPC,
                  • Some Thrift and JSON-over-HTTP
                  • Voice and video calling service was built in Elixir.
                  Data warehouse
                  • Built using open source tools including Presto, Spark, Airflow, Hadoop and Kafka.
                  Etc
                  See more