Alternatives to Envoyer logo

Alternatives to Envoyer

Istio, Envoy, linkerd, NGINX, and HAProxy are the most popular alternatives and competitors to Envoyer.
54
64
+ 1
3

What is Envoyer and what are its top alternatives?

Envoyer deploys your PHP applications with zero downtime. Just push your code, and let Envoyer deliver your application to one or many servers without interrupting a single customer. In this series, we'll discuss each feature of Envoyer, demonstrating how to use them with a sample project.
Envoyer is a tool in the Platform as a Service category of a tech stack.

Top Alternatives to Envoyer

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

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

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

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

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

  • Forge

    Forge

    Fastest possible way to host lighting-fast static websites for small businesses, web startups, and app developers. ...

  • Jenkins

    Jenkins

    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project. ...

  • Heroku

    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

Envoyer alternatives & related posts

Istio logo

Istio

644
1.1K
42
Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
644
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
  • 11
    Performance

related Istio posts

Anas MOKDAD
Shared insights
on
KongKongIstioIstio

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

See more
Envoy logo

Envoy

232
417
8
C++ front/service proxy
232
417
+ 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 · 128.1K views
    Shared insights
    on
    KubernetesKubernetesEnvoyEnvoyGoGo
    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
    EnvoyEnvoyHAProxyHAProxyTraefikTraefikNGINXNGINX

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

    linkerd

    104
    243
    7
    Twitter-Style Operability for Microservices
    104
    243
    + 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

      NGINX logo

      NGINX

      94K
      44.2K
      5.5K
      A high performance free open source web server powering busiest sites on the Internet.
      94K
      44.2K
      + 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
        Supports http/2
      • 4
        The best of them
      • 4
        Lots of Modules
      • 4
        Enterprise version
      • 4
        Great Community
      • 3
        High perfomance proxy server
      • 3
        Streaming media
      • 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
        Virtual hosting
      • 1
        Blash
      • 1
        GRPC-Web
      • 1
        Ingress controller
      • 1
        Narrow focus. Easy to configure. Fast
      • 1
        Along with Redis Cache its the Most superior
      • 0
        A
      CONS OF NGINX
      • 8
        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
      TraefikTraefikNGINXNGINX
      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
      HAProxy logo

      HAProxy

      2.2K
      1.9K
      553
      The Reliable, High Performance TCP/HTTP Load Balancer
      2.2K
      1.9K
      + 1
      553
      PROS OF HAPROXY
      • 130
        Load balancer
      • 100
        High performance
      • 69
        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
        Simple
      • 2
        Work with NTLM
      • 2
        Ssl offloading
      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
      Forge logo

      Forge

      6
      11
      1
      Static web hosting made simple
      6
      11
      + 1
      1
      PROS OF FORGE
      • 1
        Fgfgf
      CONS OF FORGE
        Be the first to leave a con

        related Forge posts

        Jenkins logo

        Jenkins

        43.2K
        35.8K
        2.2K
        An extendable open source continuous integration server
        43.2K
        35.8K
        + 1
        2.2K
        PROS OF JENKINS
        • 522
          Hosted internally
        • 465
          Free open source
        • 315
          Great to build, deploy or launch anything async
        • 243
          Tons of integrations
        • 210
          Rich set of plugins with good documentation
        • 109
          Has support for build pipelines
        • 72
          Open source and tons of integrations
        • 63
          Easy setup
        • 61
          It is open-source
        • 54
          Workflow plugin
        • 11
          Configuration as code
        • 10
          Very powerful tool
        • 9
          Many Plugins
        • 8
          Continuous Integration
        • 8
          Great flexibility
        • 8
          Git and Maven integration is better
        • 6
          Github integration
        • 6
          100% free and open source
        • 6
          Slack Integration (plugin)
        • 5
          Easy customisation
        • 5
          Self-hosted GitLab Integration (plugin)
        • 4
          Docker support
        • 3
          Excellent docker integration
        • 3
          Platform idnependency
        • 3
          Fast builds
        • 3
          Pipeline API
        • 2
          Customizable
        • 2
          Can be run as a Docker container
        • 2
          It`w worked
        • 2
          JOBDSL
        • 2
          Hosted Externally
        • 2
          It's Everywhere
        • 2
          AWS Integration
        • 1
          NodeJS Support
        • 1
          PHP Support
        • 1
          Ruby/Rails Support
        • 1
          Universal controller
        • 1
          Easily extendable with seamless integration
        • 1
          Build PR Branch Only
        CONS OF JENKINS
        • 12
          Workarounds needed for basic requirements
        • 8
          Groovy with cumbersome syntax
        • 6
          Limited abilities with declarative pipelines
        • 6
          Plugins compatibility issues
        • 5
          Lack of support
        • 4
          No YAML syntax
        • 2
          Too tied to plugins versions

        related Jenkins posts

        Tymoteusz Paul
        Devops guy at X20X Development LTD · | 23 upvotes · 4.6M views

        Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

        It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

        I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

        We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

        If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

        The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

        Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

        See more
        Thierry Schellenbach

        Releasing new versions of our services is done by Travis CI. Travis first runs our test suite. Once it passes, it publishes a new release binary to GitHub.

        Common tasks such as installing dependencies for the Go project, or building a binary are automated using plain old Makefiles. (We know, crazy old school, right?) Our binaries are compressed using UPX.

        Travis has come a long way over the past years. I used to prefer Jenkins in some cases since it was easier to debug broken builds. With the addition of the aptly named “debug build” button, Travis is now the clear winner. It’s easy to use and free for open source, with no need to maintain anything.

        #ContinuousIntegration #CodeCollaborationVersionControl

        See more
        Heroku logo

        Heroku

        20K
        15.6K
        3.2K
        Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
        20K
        15.6K
        + 1
        3.2K
        PROS OF HEROKU
        • 704
          Easy deployment
        • 460
          Free for side projects
        • 374
          Huge time-saver
        • 348
          Simple scaling
        • 261
          Low devops skills required
        • 190
          Easy setup
        • 174
          Add-ons for almost everything
        • 154
          Beginner friendly
        • 150
          Better for startups
        • 133
          Low learning curve
        • 48
          Postgres hosting
        • 41
          Easy to add collaborators
        • 30
          Faster development
        • 24
          Awesome documentation
        • 19
          Focus on product, not deployment
        • 19
          Simple rollback
        • 15
          Natural companion for rails development
        • 15
          Easy integration
        • 12
          Great customer support
        • 8
          GitHub integration
        • 6
          No-ops
        • 6
          Painless & well documented
        • 4
          Free
        • 4
          I love that they make it free to launch a side project
        • 3
          Just works
        • 3
          Great UI
        • 2
          PostgreSQL forking and following
        • 2
          MySQL extension
        • 1
          Able to host stuff good like Discord Bot
        • 0
          Sec
        • 0
          Security
        CONS OF HEROKU
        • 23
          Super expensive
        • 6
          Not a whole lot of flexibility
        • 5
          No usable MySQL option
        • 5
          Storage
        • 4
          Low performance on free tier
        • 1
          24/7 support is $1,000 per month

        related Heroku posts

        Russel Werner
        Lead Engineer at StackShare · | 30 upvotes · 1.5M views

        StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

        Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

        #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

        See more
        Simon Reymann
        Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

        Our whole DevOps stack consists of the following tools:

        • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
        • Respectively Git as revision control system
        • SourceTree as Git GUI
        • Visual Studio Code as IDE
        • CircleCI for continuous integration (automatize development process)
        • Prettier / TSLint / ESLint as code linter
        • SonarQube as quality gate
        • Docker as container management (incl. Docker Compose for multi-container application management)
        • VirtualBox for operating system simulation tests
        • Kubernetes as cluster management for docker containers
        • Heroku for deploying in test environments
        • nginx as web server (preferably used as facade server in production environment)
        • SSLMate (using OpenSSL) for certificate management
        • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
        • PostgreSQL as preferred database system
        • Redis as preferred in-memory database/store (great for caching)

        The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

        • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
        • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
        • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
        • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
        • Scalability: All-in-one framework for distributed systems.
        • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
        See more