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

Kong

461
1.1K
+ 1
130
Traefik

633
920
+ 1
82
Add tool

Kong vs Traefik: 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 Traefik? Load Balancer for Microservices. Træfɪk is a modern HTTP reverse proxy and load balancer made to deploy microservices with ease. It supports several backends (Docker, Swarm, Mesos/Marathon, Kubernetes, Consul, Etcd, Zookeeper, BoltDB, Rest API, file...) to manage its configuration automatically and dynamically.

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

"Easy to maintain" is the primary reason why developers consider Kong over the competitors, whereas "Kubernetes integration" was stated as the key factor in picking Traefik.

Kong and Traefik are both open source tools. Traefik with 23.2K GitHub stars and 2.4K forks on GitHub appears to be more popular than Kong with 22.4K GitHub stars and 2.75K GitHub forks.

According to the StackShare community, Traefik has a broader approval, being mentioned in 47 company stacks & 20 developers stacks; compared to Kong, which is listed in 50 company stacks and 14 developer stacks.

Decisions about Kong and Traefik
Gabriel Pa

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
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 138.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 Kong
Pros of Traefik
  • 36
    Easy to maintain
  • 30
    Easy to install
  • 23
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    1
  • 1
    123123
  • 1
    Documentation is clear
  • 1
    123
  • 1
    12
  • 1
    12312312
  • 19
    Kubernetes integration
  • 16
    Watch service discovery updates
  • 12
    Letsencrypt support
  • 12
    Swarm integration
  • 11
    Several backends
  • 4
    Rancher integration
  • 4
    Ready-to-use dashboard
  • 2
    Easy setup
  • 1
    Mantl integration
  • 1
    Mesos integration

Sign up to add or upvote prosMake informed product decisions

Cons of Kong
Cons of Traefik
    Be the first to leave a con
    • 7
      Complicated setup
    • 6
      Not very performant (fast)

    Sign up to add or upvote consMake informed product decisions

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

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

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

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

    What tools integrate with Kong?
    What tools integrate with Traefik?

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

    Blog Posts

    +26
    28
    15241
    What are some alternatives to Kong and Traefik?
    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