Need advice about which tool to choose?Ask the StackShare community!

Dapr

46
193
+ 1
6
Kong

464
1.1K
+ 1
130
Add tool

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.

Decisions about Dapr and Kong
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 141.9K views

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.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Dapr
Pros of Kong
  • 2
    Manage inter-service state
  • 2
    Zipkin app tracing "for free"
  • 1
    MTLS "for free"
  • 1
    App dashboard for rapid log overview
  • 36
    Easy to maintain
  • 30
    Easy to install
  • 24
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    Documentation is clear
  • 1
    1
  • 1
    123123
  • 1
    12312312
  • 1
    123
  • 1
    12

Sign up to add or upvote prosMake informed product decisions

Sign up to add or upvote consMake informed product decisions

What is Dapr?

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.

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.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Dapr?
What companies use Kong?
    No companies found
    See which teams inside your own company are using Dapr or Kong.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Dapr?
    What tools integrate with Kong?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    +26
    28
    15253
    What are some alternatives to Dapr and Kong?
    Istio
    Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc.
    Akka
    Akka is a toolkit and runtime for building highly concurrent, distributed, and resilient message-driven applications on the JVM.
    Orleans
    Orleans is a framework that provides a straightforward approach to building distributed high-scale computing applications, without the need to learn and apply complex concurrency or other scaling patterns. It was created by Microsoft Research and designed for use in the cloud.
    Knative
    Knative provides a set of middleware components that are essential to build modern, source-centric, and container-based applications that can run anywhere: on premises, in the cloud, or even in a third-party data center
    Envoy
    Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
    See all alternatives