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. API Gateway
  5. Kong vs Micro

Kong vs Micro

OverviewDecisionsComparisonAlternatives

Overview

Kong
Kong
Stacks671
Followers1.5K
Votes139
GitHub Stars42.1K
Forks5.0K
Micro
Micro
Stacks89
Followers55
Votes2

Kong vs Micro: What are the differences?

What is 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.

What is Micro? A microservice toolkit. Micro provides the core requirements for building and managing microservices. It consists of a set of libraries and tools which are primarily geared towards development in the programming language Go, however looks to solve for other languages via HTTP using a Sidecar.

Kong and Micro 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, Micro provides the following key features:

  • API
  • CLI
  • Web UI

Kong and Micro are both open source tools. It seems that Kong with 22.4K GitHub stars and 2.75K forks on GitHub has more adoption than Micro with 6.45K GitHub stars and 528 GitHub forks.

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 Kong, Micro

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

Detailed Comparison

Kong
Kong
Micro
Micro

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.

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

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; IP-restriction: Whitelist or blacklist IPs that can make requests; Authentication: Manage consumer credentials query string and header tokens; Rate-limiting: Block and throttle requests based on IP or authentication; Transformations: Add, remove or manipulate HTTP params and headers on-the-fly; CORS: Enable cross-origin requests to your APIs that would otherwise be blocked; Anything: Need custom functionality? Extend Kong with your own Lua plugins;
Authentication; Config Management; Key-Value Storage; API Gateway; Service Discovery; Event Streaming
Statistics
GitHub Stars
42.1K
GitHub Stars
-
GitHub Forks
5.0K
GitHub Forks
-
Stacks
671
Stacks
89
Followers
1.5K
Followers
55
Votes
139
Votes
2
Pros & Cons
Pros
  • 37
    Easy to maintain
  • 32
    Easy to install
  • 26
    Flexible
  • 21
    Great performance
  • 7
    Api blueprint
Pros
  • 1
    Nice tooling
  • 1
    Great flexibility
Integrations
Cassandra
Cassandra
Docker
Docker
Prometheus
Prometheus
Kubernetes
Kubernetes
PostgreSQL
PostgreSQL
NGINX
NGINX
Vagrant
Vagrant
No integrations available

What are some alternatives to Kong, Micro?

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.

Amazon API Gateway

Amazon API Gateway

Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management.

Tyk Cloud

Tyk Cloud

Tyk is a leading Open Source API Gateway and Management Platform, featuring an API gateway, analytics, developer portal and dashboard. We power billions of transactions for thousands of innovative organisations.

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.

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

Postman
Swagger UI

Postman vs Swagger UI

gulp
Grunt

Grunt vs Webpack vs gulp