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. Dactory vs Kuma

Dactory vs Kuma

OverviewDecisionsComparisonAlternatives

Overview

Kuma
Kuma
Stacks16
Followers95
Votes0
GitHub Stars2.3K
Forks169
Dactory
Dactory
Stacks0
Followers7
Votes0

Kuma vs Dactory: What are the differences?

Kuma: Build, Secure and Observe your modern Service Mesh. It is a universal open source control-plane for Service Mesh and Microservices that can run and be operated natively across both Kubernetes and VM environments, in order to be easily adopted by every team in the organization; Dactory: Golang GRPC microservice code generator. Generate code for Golang microservices using a simple web interface. The generated code provides a microservices project based on GRPC and an Envoy gateway. This way you can focus on the actual business logic and not on all the boilerplate code that is required to get microservices up and running.

Kuma and Dactory can be categorized as "Microservices" tools.

Some of the features offered by Kuma are:

  • Universal Control Plane
  • Lightweight Data Plane
  • Automatic

On the other hand, Dactory provides the following key features:

  • Golang code generation including configuration of Envoy gateway
  • Easy dev deployment of your microservices using Docker Compose
  • Easy to use web interface

Kuma is an open source tool with 987 GitHub stars and 47 GitHub forks. Here's a link to Kuma's open source repository on GitHub.

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 Kuma, Dactory

Mohammed
Mohammed

CTO at Famcare

Jan 16, 2020

Needs advice

One of our applications is currently migrating to AWS, and we need to make a decision between using AWS API Gateway with AWS App Mesh, or Kong API Gateway with Kuma.

Some people advise us to benefit from AWS managed services, while others raise the vendor lock issue. So, I need your advice on that, and if there is any other important factor rather than vendor locking that I must take into consideration.

38.7k views38.7k
Comments

Detailed Comparison

Kuma
Kuma
Dactory
Dactory

It is a universal open source control-plane for Service Mesh and Microservices that can run and be operated natively across both Kubernetes and VM environments, in order to be easily adopted by every team in the organization.

Generate code for Golang microservices using a simple web interface. The generated code provides a Golang microservices project based on GRPC and scripts to deploy it using container technology (Docker).

Universal Control Plane; Lightweight Data Plane; Automatic; Multi-Tenancy; Network Security; Traffic Segmentation: With flexible ACL rules
Get microservices up and running in minutes; Golang code generation ; GRPC gateway configuration; Easy deployment of your microservices using Docker Compose; Easy to use web interface
Statistics
GitHub Stars
2.3K
GitHub Stars
-
GitHub Forks
169
GitHub Forks
-
Stacks
16
Stacks
0
Followers
95
Followers
7
Votes
0
Votes
0
Integrations
YAML
YAML
CentOS
CentOS
Kubernetes
Kubernetes
PostgreSQL
PostgreSQL
Red Hat Enterprise Linux (RHEL)
Red Hat Enterprise Linux (RHEL)
macOS
macOS
Debian
Debian
Ubuntu
Ubuntu
Golang
Golang
gRPC
gRPC

What are some alternatives to Kuma, Dactory?

Istio

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.

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.

Dapr

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.

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.

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