Kong vs Dapr: What are the differences?
Developers describe Kong as "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. On the other hand, Dapr is detailed as "An open-source project to make it easier to build microservices". It is a portable, event-driven runtime that makes it easy for developers to build resilient, stateless and stateful microservices that run on the cloud and edge and embraces the diversity of languages and developer frameworks.
Kong and Dapr can be categorized as "Microservices" tools.
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, Dapr provides the following key features:
- Event-driven Pub-Sub system with pluggable providers and at-least-once semantics
- Input and Output bindings with pluggable providers
- State management with pluggable data stores
Kong and Dapr are both open source tools. Kong with 23.8K GitHub stars and 2.98K forks on GitHub appears to be more popular than Dapr with 3.44K GitHub stars and 137 GitHub forks.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Dapr?
What is Kong?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Dapr?
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