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.
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!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions