Istio vs Kong vs Micro
Overview
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.
CLI (Node.js)
Manual
Detailed Comparison
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 | 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. |
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 Stars 37.6K |
GitHub Forks 5.0K | GitHub Forks - | GitHub Forks 8.1K |
Stacks 671 | Stacks 89 | Stacks 2.3K |
Followers 1.5K | Followers 55 | Followers 1.5K |
Votes 139 | Votes 2 | Votes 54 |
Pros & Cons | ||
Pros
| Pros
| Pros
Cons
|
Integrations | ||
| No integrations available | ||
What are some alternatives to Kong, Micro, Istio?
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 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 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
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
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
It is a JavaScript framework for writing data-centric HTTP microservices that run directly inside of ArangoDB.
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
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 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
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.
