StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Infrastructure as a Service
  4. Load Balancer Reverse Proxy
  5. Envoy vs F5 BIG-IP

Envoy vs F5 BIG-IP

OverviewComparisonAlternatives

Overview

F5 BIG-IP
F5 BIG-IP
Stacks50
Followers64
Votes0
Envoy
Envoy
Stacks304
Followers546
Votes9
GitHub Stars27.0K
Forks5.1K

Envoy vs F5 BIG-IP: What are the differences?

Introduction

In this article, we will compare the key differences between Envoy and F5 BIG-IP. Both Envoy and F5 BIG-IP are popular solutions for load balancing and proxying. However, there are several distinct features that set them apart from each other. Let's explore these differences in detail.

  1. Deployment Model: Envoy is commonly used as a sidecar proxy, meaning it runs alongside a service to provide proxying and load balancing functionality. On the other hand, F5 BIG-IP is typically deployed as a dedicated network appliance, providing load balancing, security, and application acceleration features.

  2. Platform Support: Envoy is designed to be a cloud-native solution and has excellent support for containerized environments, including Kubernetes. It is also platform-agnostic and can be deployed on various operating systems. F5 BIG-IP, on the other hand, is primarily focused on traditional on-premises deployments and provides extensive support for a wide range of hardware platforms.

  3. Configuration Approach: Envoy utilizes a declarative configuration approach, where the desired state of the proxy is defined and the management server converges the proxy to the desired state. This allows for dynamic and automated configuration updates. In contrast, F5 BIG-IP relies on a more traditional imperative configuration approach, where configurations are made directly to the devices through a management interface.

  4. Flexibility and Extensibility: Envoy is known for its flexibility and extensibility. It offers an extensive plugin architecture and supports a wide range of filters and extensions that can be customized to meet specific requirements. F5 BIG-IP also provides extensibility through iRules, which allow custom scripting of traffic policies, but it may have limitations compared to the versatility of Envoy's plugin system.

  5. Community and Open Source: Envoy has a thriving open-source community, with regular contributions from various organizations and individuals. This active community fosters continuous development and innovation. F5 BIG-IP, on the other hand, is a proprietary solution with a more limited open-source ecosystem.

  6. Pricing and Licensing: Envoy is open-source and available under the Apache License 2.0, making it a cost-effective option for many organizations. F5 BIG-IP, being a commercial product, requires a license to use and is usually associated with higher costs.

In summary, Envoy and F5 BIG-IP differ in their deployment models, platform support, configuration approaches, flexibility and extensibility, community involvement, and pricing and licensing. These differences allow organizations to choose the solution that best fits their specific needs and requirements.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

F5 BIG-IP
F5 BIG-IP
Envoy
Envoy

It ensures that applications are always secure and perform the way they should. You get built-in security, traffic management, and performance application services, whether your applications live in a private data center or in the cloud.

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.

Statistics
GitHub Stars
-
GitHub Stars
27.0K
GitHub Forks
-
GitHub Forks
5.1K
Stacks
50
Stacks
304
Followers
64
Followers
546
Votes
0
Votes
9
Pros & Cons
No community feedback yet
Pros
  • 9
    GRPC-Web

What are some alternatives to F5 BIG-IP, Envoy?

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.

AWS Elastic Load Balancing (ELB)

AWS Elastic Load Balancing (ELB)

With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task.

Fly

Fly

Deploy apps through our global load balancer with minimal shenanigans. All Fly-enabled applications get free SSL certificates, accept traffic through our global network of datacenters, and encrypt all traffic from visitors through to application servers.

Hipache

Hipache

Hipache is a distributed proxy designed to route high volumes of http and websocket traffic to unusually large numbers of virtual hosts, in a highly dynamic topology where backends are added and removed several times per second. It is particularly well-suited for PaaS (platform-as-a-service) and other environments that are both business-critical and multi-tenant.

node-http-proxy

node-http-proxy

node-http-proxy is an HTTP programmable proxying library that supports websockets. It is suitable for implementing components such as proxies and load balancers.

Modern DDoS Protection & Edge Security Platform

Modern DDoS Protection & Edge Security Platform

Protect and accelerate your apps with Trafficmind’s global edge — DDoS defense, WAF, API security, CDN/DNS, 99.99% uptime and 24/7 expert team.

DigitalOcean Load Balancer

DigitalOcean Load Balancer

Load Balancers are a highly available, fully-managed service that work right out of the box and can be deployed as fast as a Droplet. Load Balancers distribute incoming traffic across your infrastructure to increase your application's availability.

Google Cloud Load Balancing

Google Cloud Load Balancing

You can scale your applications on Google Compute Engine from zero to full-throttle with it, with no pre-warming needed. You can distribute your load-balanced compute resources in single or multiple regions, close to your users and to meet your high availability requirements.

GLBC

GLBC

It is a GCE L7 load balancer controller that manages external loadbalancers configured through the Kubernetes Ingress API.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana