Need advice about which tool to choose?Ask the StackShare community!
Kong vs linkerd: What are the differences?
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; linkerd: Twitter-Style Operability for Microservices. 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.
Kong and linkerd belong to "Microservices Tools" category of the tech stack.
Some of the features offered by Kong are:
- Logging: Log requests and responses to your system over TCP, UDP or to disk
- OAuth2.0: Add easily an OAuth2.0 authentication to your APIs
- Monitoring: Live monitoring provides key load and performance server metrics
On the other hand, linkerd provides the following key features:
- Adaptive load-balancing
- Fine-grained instrumentation
- Abstractions over service discovery
Kong and linkerd are both open source tools. Kong with 22.2K GitHub stars and 2.71K forks on GitHub appears to be more popular than linkerd with 5K GitHub stars and 499 GitHub forks.
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 Kong
- Easy to maintain37
- Easy to install32
- Flexible26
- Great performance21
- Api blueprint6
- Custom Plugins4
- Kubernetes-native3
- Security2
- Has a good plugin infrastructure2
- Agnostic2
- Load balancing1
- Documentation is clear1
- Very customizable1
Pros of linkerd
- CNCF Project3
- Service Mesh1
- Fast Integration1
- Pre-check permissions1
- Light Weight1
Sign up to add or upvote prosMake informed product decisions
What is Kong?
What is linkerd?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Kong?
What companies use linkerd?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Kong?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+26