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

HAProxy

2.2K
1.9K
+ 1
553
Kong

481
1.2K
+ 1
130
Add tool

HAProxy vs Kong: What are the differences?

HAProxy: The Reliable, High Performance TCP/HTTP Load Balancer. 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; Kong: Open Source Microservice & API Management Layer. 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.

HAProxy and Kong are primarily classified as "Load Balancer / Reverse Proxy" and "Microservices" tools respectively.

"Load balancer" is the top reason why over 118 developers like HAProxy, while over 28 developers mention "Easy to maintain" as the leading cause for choosing Kong.

Kong is an open source tool with 22.4K GitHub stars and 2.75K GitHub forks. Here's a link to Kong's open source repository on GitHub.

Instagram, Dropbox, and Medium are some of the popular companies that use HAProxy, whereas Kong is used by Checkr, Policygenius, and Decision6. HAProxy has a broader approval, being mentioned in 457 company stacks & 211 developers stacks; compared to Kong, which is listed in 50 company stacks and 14 developer stacks.

Decisions about HAProxy and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 158.7K 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
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of HAProxy
Pros of Kong
  • 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
  • 36
    Easy to maintain
  • 30
    Easy to install
  • 24
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    Documentation is clear
  • 1
    1
  • 1
    123123
  • 1
    12312312
  • 1
    123
  • 1
    12

Sign up to add or upvote prosMake informed product decisions

Cons of HAProxy
Cons of Kong
  • 3
    Becomes your single point of failure
    Be the first to leave a con

    Sign up to add or upvote consMake informed product decisions

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

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

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

    What companies use HAProxy?
    What companies use Kong?
    See which teams inside your own company are using HAProxy or Kong.
    Sign up for Private StackShareLearn More

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

    What tools integrate with HAProxy?
    What tools integrate with Kong?

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

    Blog Posts

    GitHubGitSlack+30
    25
    15787
    GitHubPythonNode.js+26
    28
    15369
    DockerSlackAmazon EC2+17
    18
    5675
    GitHubSlackMySQL+44
    109
    50189
    What are some alternatives to HAProxy and Kong?
    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.
    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.
    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.
    Squid
    Squid reduces bandwidth and improves response times by caching and reusing frequently-requested web pages. Squid has extensive access controls and makes a great server accelerator. It runs on most available operating systems, including Windows and is licensed under the GNU GPL.
    Varnish
    Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture.
    See all alternatives