Need advice about which tool to choose?Ask the StackShare community!
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
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.
Pros of Ambassador
- Edge-proxy2
- Kubernetes friendly configuration1
Pros of Kong
- Easy to maintain36
- Easy to install30
- Flexible22
- Great performance20
- Api blueprint5
- Custom Plugins4
- Kubernetes-native3
- Agnostic2
- Documentation is clear1
- 11
- 120
- 1231230
- 1230
- 123123120
Pros of Traefik
- Kubernetes integration19
- Watch service discovery updates16
- Swarm integration12
- Letsencrypt support12
- Several backends11
- Ready-to-use dashboard4
- Rancher integration4
- Easy setup2
- Mantl integration1
- Mesos integration1
Sign up to add or upvote prosMake informed product decisions
Cons of Ambassador
Cons of Kong
Cons of Traefik
- Complicated setup7
- Not very performant (fast)6