Kong vs. Traefik

  • -
  • 20
  • 237
  • -
  • 6
  • 881

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?

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.
Why do developers choose Kong?
Why do you like Kong?

Why do developers choose Traefik?
Why do you like Traefik?

What are the cons of using Kong?
No Cons submitted yet for Kong
Downsides of Kong?

What are the cons of using Traefik?
Downsides of Traefik?

Want advice about which of these to choose?Ask the StackShare community!

How much does Kong cost?
How much does Traefik cost?
What companies use Kong?
66 companies on StackShare use Kong
What companies use Traefik?
55 companies on StackShare use Traefik
What tools integrate with Kong?
8 tools on StackShare integrate with Kong
No integrations listed yet

What are some alternatives to Kong and Traefik?

  • Istio - Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
  • Express Gateway - An open source API gateway for microservices built on Express.js
  • linkerd - Twitter-Style Operability for Microservices
  • seneca - A Micro-Services toolkit for Node.js

See all alternatives to Kong

MesosCon Wrap Up
Kong Presents at MesosCon 2017
Kong CE 0.11.0 released
Setting up Traefik as a Dynamically-Configured Proxy...

Interest Over Time