Kong vs Varnish

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

Kong

513
1.3K
+ 1
128
Varnish

11.7K
2.1K
+ 1
359
Add tool

Kong vs Varnish: What are the differences?

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

What is Varnish? High-performance HTTP accelerator. 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.

Kong belongs to "Microservices Tools" category of the tech stack, while Varnish can be primarily classified under "Web Cache".

"Easy to maintain" is the primary reason why developers consider Kong over the competitors, whereas "High-performance" was stated as the key factor in picking Varnish.

Kong and Varnish are both open source tools. It seems that Kong with 22.2K GitHub stars and 2.71K forks on GitHub has more adoption than Varnish with 908 GitHub stars and 216 GitHub forks.

According to the StackShare community, Varnish has a broader approval, being mentioned in 1003 company stacks & 135 developers stacks; compared to Kong, which is listed in 50 company stacks and 13 developer stacks.

Decisions about Kong and Varnish
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 193.4K 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 StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Kong
Pros of Varnish
  • 36
    Easy to maintain
  • 31
    Easy to install
  • 24
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    Security
  • 1
    Documentation is clear
  • 1
    Load balancing
  • 103
    High-performance
  • 66
    Very Fast
  • 56
    Very Stable
  • 43
    Very Robust
  • 36
    HTTP reverse proxy
  • 20
    Open Source
  • 17
    Web application accelerator
  • 10
    Easy to config
  • 4
    Widely Used
  • 3
    Great community
  • 1
    Essential software for HTTP

Sign up to add or upvote prosMake informed product decisions

- No public GitHub repository available -

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.

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

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

Jobs that mention Kong and Varnish as a desired skillset
CBRE
United Kingdom of Great Britain and Northern Ireland England London
CBRE
United Kingdom of Great Britain and Northern Ireland England Gloucester
CBRE
United Kingdom of Great Britain and Northern Ireland England London
CBRE
United Kingdom of Great Britain and Northern Ireland England London
CBRE
United Kingdom of Great Britain and Northern Ireland England London
What companies use Kong?
What companies use Varnish?
See which teams inside your own company are using Kong or Varnish.
Sign up for StackShare EnterpriseLearn More

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

What tools integrate with Kong?
What tools integrate with Varnish?

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

Blog Posts

May 6 2020 at 6:34AM

Pinterest

JavaScriptC++Varnish+6
4
2791
GitHubPythonNode.js+26
29
15526
What are some alternatives to Kong and Varnish?
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.
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.
Zuul
It is the front door for all requests from devices and websites to the backend of the Netflix streaming application. As an edge service application, It is built to enable dynamic routing, monitoring, resiliency, and security. Routing is an integral part of a microservice architecture.
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.
Jersey
It is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. It provides it’s own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development.
See all alternatives