Alternatives to Envoy logo

Alternatives to Envoy

Istio, NGINX, linkerd, Trailblazer, and HAProxy are the most popular alternatives and competitors to Envoy.
219
386
+ 1
8

What is Envoy and what are its top alternatives?

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.
Envoy is a tool in the Load Balancer / Reverse Proxy category of a tech stack.
Envoy is an open source tool with 17.5K GitHub stars and 3.2K GitHub forks. Here’s a link to Envoy's open source repository on GitHub

Top Alternatives to Envoy

  • Istio

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

  • NGINX

    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

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

  • Trailblazer

    Trailblazer

    Trailblazer is a thin layer on top of Rails. It gently enforces encapsulation, an intuitive code structure and gives you an object-oriented architecture. In a nutshell: Trailblazer makes you write logicless models that purely act as data objects, don't contain callbacks, nested attributes, validations or domain logic. It removes bulky controllers and strong_parameters by supplying additional layers to hold that code and completely replaces helpers. ...

  • HAProxy

    HAProxy

    HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. ...

  • Traefik

    Traefik

    A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically. ...

  • Consul

    Consul

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

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

Envoy alternatives & related posts

Istio logo

Istio

606
1.1K
42
Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
606
1.1K
+ 1
42
PROS OF ISTIO
  • 11
    Zero code for logging and monitoring
  • 8
    Service Mesh
  • 7
    Great flexibility
  • 4
    Ingress controller
  • 3
    Resiliency
  • 3
    Easy integration with Kubernetes and Docker
  • 3
    Full Security
  • 3
    Powerful authorization mechanisms
CONS OF ISTIO
  • 10
    Performance

related Istio posts

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
NGINX logo

NGINX

89.6K
40.3K
5.5K
A high performance free open source web server powering busiest sites on the Internet.
89.6K
40.3K
+ 1
5.5K
PROS OF NGINX
  • 1.4K
    High-performance http server
  • 896
    Performance
  • 728
    Easy to configure
  • 606
    Open source
  • 529
    Load balancer
  • 286
    Scalability
  • 285
    Free
  • 222
    Web server
  • 173
    Simplicity
  • 134
    Easy setup
  • 29
    Content caching
  • 19
    Web Accelerator
  • 14
    Capability
  • 13
    Fast
  • 11
    Predictability
  • 10
    High-latency
  • 7
    Reverse Proxy
  • 6
    Fast and lightweight
  • 6
    Supports http/2
  • 4
    Enterprise version
  • 4
    Great Community
  • 4
    Lots of Modules
  • 4
    The best of them
  • 3
    Streaming media
  • 3
    High perfomance proxy server
  • 3
    Embedded Lua scripting
  • 3
    Reversy Proxy
  • 3
    Streaming media delivery
  • 2
    Fast and easy to set up
  • 2
    Lightweight
  • 2
    Slim
  • 2
    saltstack
  • 1
    GRPC-Web
  • 1
    Virtual hosting
  • 1
    Narrow focus. Easy to configure. Fast
  • 1
    Along with Redis Cache its the Most superior
  • 1
    Ingress controller
  • 0
    A
CONS OF NGINX
  • 7
    Advanced features require subscription

related NGINX posts

Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

See more
Gabriel Pa
Shared insights
on
Traefik
NGINX
at

We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

See more
linkerd logo

linkerd

92
223
7
Twitter-Style Operability for Microservices
92
223
+ 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

    Trailblazer logo

    Trailblazer

    16
    24
    13
    A new architecture for Rails.
    16
    24
    + 1
    13
    PROS OF TRAILBLAZER
    • 5
      Trailblazer allows creating sane, large apps in Rails
    • 3
      Separates business logic from framework
    • 2
      Sound Software Architecture principals
    • 2
      Improves maintainability
    • 1
      Makes Rails better
    CONS OF TRAILBLAZER
    • 1
      Hasn't been on Thoughtworks radar since 2014

    related Trailblazer posts

    HAProxy logo

    HAProxy

    2.2K
    1.8K
    551
    The Reliable, High Performance TCP/HTTP Load Balancer
    2.2K
    1.8K
    + 1
    551
    PROS OF HAPROXY
    • 129
      Load balancer
    • 100
      High performance
    • 68
      Very fast
    • 57
      Proxying for tcp and http
    • 55
      SSL termination
    • 30
      Open source
    • 27
      Reliable
    • 20
      Free
    • 18
      Well-Documented
    • 12
      Very popular
    • 7
      Suited for very high traffic web sites
    • 7
      Runs health checks on backends
    • 6
      Scalable
    • 5
      Ready to Docker
    • 4
      Powers many world's most visited sites
    • 2
      Work with NTLM
    • 2
      Ssl offloading
    • 2
      Simple
    CONS OF HAPROXY
    • 3
      Becomes your single point of failure

    related HAProxy posts

    Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

    See more
    Tom Klein

    We're using Git through GitHub for public repositories and GitLab for our private repositories due to its easy to use features. Docker and Kubernetes are a must have for our highly scalable infrastructure complimented by HAProxy with Varnish in front of it. We are using a lot of npm and Visual Studio Code in our development sessions.

    See more
    Traefik logo

    Traefik

    603
    888
    82
    The Cloud Native Edge Router
    603
    888
    + 1
    82
    PROS OF TRAEFIK
    • 19
      Kubernetes integration
    • 16
      Watch service discovery updates
    • 12
      Swarm integration
    • 12
      Letsencrypt support
    • 11
      Several backends
    • 4
      Ready-to-use dashboard
    • 4
      Rancher integration
    • 2
      Easy setup
    • 1
      Mantl integration
    • 1
      Mesos integration
    CONS OF TRAEFIK
    • 7
      Complicated setup
    • 6
      Not very performant (fast)

    related Traefik posts

    Gabriel Pa
    Shared insights
    on
    Traefik
    NGINX
    at

    We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

    We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

    The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

    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
    Consul logo

    Consul

    990
    1.2K
    204
    A tool for service discovery, monitoring and configuration
    990
    1.2K
    + 1
    204
    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
    • 2
      Not Java
    • 1
      Docker integration
    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
      Kubernetes logo

      Kubernetes

      34.8K
      29.2K
      617
      Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
      34.8K
      29.2K
      + 1
      617
      PROS OF KUBERNETES
      • 154
        Leading docker container management solution
      • 123
        Simple and powerful
      • 97
        Open source
      • 74
        Backed by google
      • 56
        The right abstractions
      • 24
        Scale services
      • 18
        Replication controller
      • 9
        Permission managment
      • 7
        Simple
      • 7
        Supports autoscaling
      • 6
        Cheap
      • 4
        No cloud platform lock-in
      • 4
        Reliable
      • 4
        Self-healing
      • 3
        Promotes modern/good infrascture practice
      • 3
        Open, powerful, stable
      • 3
        Quick cloud setup
      • 3
        Scalable
      • 2
        Runs on azure
      • 2
        Cloud Agnostic
      • 2
        Backed by Red Hat
      • 2
        Custom and extensibility
      • 2
        Captain of Container Ship
      • 2
        A self healing environment with rich metadata
      • 1
        Golang
      • 1
        Expandable
      • 1
        Everything of CaaS
      • 1
        Sfg
      • 1
        Easy setup
      • 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.8M 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