StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. API Tools
  4. Microservices Tools
  5. Dapr vs Istio

Dapr vs Istio

OverviewDecisionsComparisonAlternatives

Overview

Istio
Istio
Stacks2.3K
Followers1.5K
Votes54
GitHub Stars37.6K
Forks8.1K
Dapr
Dapr
Stacks96
Followers336
Votes9
GitHub Stars25.2K
Forks2.0K

Dapr vs Istio: What are the differences?

Dapr and Istio are both popular open-source projects used in the field of microservices and cloud-native applications. Let's explore the key differences between them.

  1. Deployment and Orchestration: Dapr focuses primarily on providing a runtime platform for building resilient microservices applications, whereas Istio is primarily focused on the service mesh layer, providing traffic management and observability features. Dapr can be deployed on various orchestrators like Kubernetes, while Istio is designed specifically for Kubernetes.

  2. Programming Models: Dapr provides a set of building blocks and runtime abstractions that make it easier to develop microservices applications, regardless of the underlying programming language or framework. It supports a variety of programming models like HTTP, gRPC, and Actors, making it flexible for developers. In contrast, Istio does not provide specific programming models but focuses on handling network traffic and security aspects of service-to-service communication.

  3. Service Discovery: Dapr provides a built-in service discovery mechanism, allowing services to discover and communicate with each other without any extra configuration. It dynamically updates service endpoints, making it easier to scale and manage microservices. On the other hand, Istio relies on Kubernetes DNS or external service discovery mechanisms for service discovery.

  4. Traffic Management: Istio offers advanced traffic management capabilities like intelligent routing, load balancing, and fault injection. It allows you to define routing rules and control the traffic flow between services using features like circuit breakers and retries. Dapr, on the other hand, does not provide native traffic management features but can be used with service meshes like Istio for advanced traffic management capabilities.

  5. Observability: Istio provides powerful observability features like distributed tracing, logging, and metrics collection, which can help in monitoring and troubleshooting microservices applications. It integrates with popular observability tools like Jaeger and Prometheus. Dapr also provides observability features like distributed tracing and metrics, but they are not as extensive as Istio.

  6. Security: Istio offers robust security features like mutual TLS authentication, authorization policies, and encryption of traffic between services. It provides fine-grained control over service-to-service communication and can enforce security policies at the network level. Dapr also offers security features like encryption but does not provide the same level of fine-grained control and policy enforcement capabilities as Istio.

In summary, Dapr focuses on providing a runtime platform and flexible programming models for building microservices applications, while Istio specializes in service mesh capabilities for traffic management, observability, and security.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Istio, Dapr

Prateek
Prateek

Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic

Mar 14, 2020

Decided

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.

322k views322k
Comments
lyc218
lyc218

Feb 21, 2020

Needs advice

Envoy proxy is widely adopted in many companies for service mesh proxy, but it utilizes BoringSSL by default. Red Hat OpenShift fork envoy branch with their own OpenSSL support, I wonder any other companies are also using envoy-openssl branch for compatibility? How about AWS App Mesh?

Any input would be much appreciated!

42.8k views42.8k
Comments

Detailed Comparison

Istio
Istio
Dapr
Dapr

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.

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.

-
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; Consistent service-to-service discovery and invocation; Opt-in stateful models: Strong/Eventual consistency, First-write/Last-write wins; Cross platform Virtual Actors; Rate limiting; Built-in distributed tracing using Open Telemetry; Runs natively on Kubernetes using a dedicated Operator and CRDs; Supports all programming languages via HTTP and gRPC; Multi-Cloud, open components (bindings, pub-sub, state) from Azure, AWS, GCP; Runs anywhere - as a process or containerized; Lightweight (58MB binary, 4MB physical memory); Runs as a sidecar - removes the need for special SDKs or libraries; Dedicated CLI - developer friendly experience with easy debugging; Clients for Java, Dotnet, Go, Javascript and Python
Statistics
GitHub Stars
37.6K
GitHub Stars
25.2K
GitHub Forks
8.1K
GitHub Forks
2.0K
Stacks
2.3K
Stacks
96
Followers
1.5K
Followers
336
Votes
54
Votes
9
Pros & Cons
Pros
  • 14
    Zero code for logging and monitoring
  • 9
    Service Mesh
  • 8
    Great flexibility
  • 5
    Ingress controller
  • 5
    Resiliency
Cons
  • 17
    Performance
Pros
  • 3
    Manage inter-service state
  • 2
    Zipkin app tracing "for free"
  • 2
    MTLS "for free"
  • 2
    App dashboard for rapid log overview
Cons
  • 1
    Additional overhead
Integrations
Kubernetes
Kubernetes
Docker
Docker
.NET Core
.NET Core
Java
Java
Python
Python
Microsoft Azure
Microsoft Azure
Kubernetes
Kubernetes
JavaScript
JavaScript
Google Cloud Platform
Google Cloud Platform
Golang
Golang

What are some alternatives to Istio, Dapr?

Azure Service Fabric

Azure Service Fabric

Azure Service Fabric is a distributed systems platform that makes it easy to package, deploy, and manage scalable and reliable microservices. Service Fabric addresses the significant challenges in developing and managing cloud apps.

Moleculer

Moleculer

It is a fault tolerant framework. It has built-in load balancer, circuit breaker, retries, timeout and bulkhead features. It is open source and free of charge project.

Express Gateway

Express Gateway

A cloud-native microservices gateway completely configurable and extensible through JavaScript/Node.js built for ALL platforms and languages. Enterprise features are FREE thanks to the power of 3K+ ExpressJS battle hardened modules.

ArangoDB Foxx

ArangoDB Foxx

It is a JavaScript framework for writing data-centric HTTP microservices that run directly inside of ArangoDB.

Zuul

Zuul

It is the front door for all requests from devices and websites to the backend of the Netflix streaming application. As an edge service application, It is built to enable dynamic routing, monitoring, resiliency, and security. Routing is an integral part of a microservice architecture.

linkerd

linkerd

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.

Jersey

Jersey

It is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. It provides it’s own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development.

Ocelot

Ocelot

It is aimed at people using .NET running a micro services / service oriented architecture that need a unified point of entry into their system. However it will work with anything that speaks HTTP and run on any platform that ASP.NET Core supports. It manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service.

Micro

Micro

Micro is a framework for cloud native development. Micro addresses the key requirements for building cloud native services. It leverages the microservices architecture pattern and provides a set of services which act as the building blocks

Claudia

Claudia

Claudia helps you deploy Node.js microservices to Amazon Web Services easily. It automates and simplifies deployment workflows and error prone tasks, so you can focus on important problems and not have to worry about AWS service quirks.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana