Need advice about which tool to choose?Ask the StackShare community!
Manage your open source components, licenses, and vulnerabilities
Learn MorePros of Istio
Pros of Kong
Pros of Micro
Pros of Istio
- Zero code for logging and monitoring14
- Service Mesh9
- Great flexibility8
- Resiliency5
- Powerful authorization mechanisms5
- Ingress controller5
- Easy integration with Kubernetes and Docker4
- Full Security4
Pros of Kong
- Easy to maintain37
- Easy to install32
- Flexible26
- Great performance21
- Api blueprint7
- Custom Plugins4
- Kubernetes-native3
- Security2
- Has a good plugin infrastructure2
- Agnostic2
- Load balancing1
- Documentation is clear1
- Very customizable1
Pros of Micro
- Great flexibility1
- Nice tooling1
Sign up to add or upvote prosMake informed product decisions
Cons of Istio
Cons of Kong
Cons of Micro
Cons of Istio
- Performance17
Cons of Kong
Be the first to leave a con
Cons of Micro
Be the first to leave a con
Sign up to add or upvote consMake informed product decisions
What is 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.
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.
What is 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
Need advice about which tool to choose?Ask the StackShare community!
Jobs that mention Istio, Kong, and Micro as a desired skillset
What companies use Istio?
What companies use Kong?
What companies use Micro?
What companies use Micro?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Istio?
What tools integrate with Kong?
What tools integrate with Micro?
What tools integrate with Istio?
What tools integrate with Kong?
What tools integrate with Micro?
No integrations found
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+26 29
16247
What are some alternatives to Istio, Kong, and Micro?
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.
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.
Kubernetes
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
Conduit
Conduit is a lightweight open source service mesh designed for performance, power, and ease of use when running applications on Kubernetes. Conduit is incredibly fast, lightweight, fundamentally secure, and easy to get started with.
AWS App Mesh
AWS App Mesh is a service mesh based on the Envoy proxy that makes it easy to monitor and control containerized microservices. App Mesh standardizes how your microservices communicate, giving you end-to-end visibility and helping to ensure high-availability for your applications. App Mesh gives you consistent visibility and network traffic controls for every microservice in an application. You can use App Mesh with Amazon ECS (using the Amazon EC2 launch type), Amazon EKS, and Kubernetes on AWS.