Need advice about which tool to choose?Ask the StackShare community!

Istio

Stacks949

Followers1.5K

+ 1

Votes54

Micro

Stacks75

Followers55

+ 1

Votes2

Add tool

Istio vs Micro: What are the differences?

Istio: Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft. 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; 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.

Istio and Micro can be categorized as "Microservices" tools.

Istio and Micro are both open source tools. It seems that Istio with 18.5K GitHub stars and 3.1K forks on GitHub has more adoption than Micro with 6.45K GitHub stars and 528 GitHub forks.

Decisions about Istio and Micro

Prateek Mittal

Chose

Istio

over

Kong

Traefik

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.

Manage your open source components, licenses, and vulnerabilities

Learn More

Pros of Istio

Pros of Micro

14
Zero code for logging and monitoring
9
Service Mesh
8
Great flexibility
5
Resiliency
5
Powerful authorization mechanisms
5
Ingress controller
4
Easy integration with Kubernetes and Docker
4
Full Security

1
Great flexibility
1
Nice tooling

Sign up to add or upvote prosMake informed product decisions

Cons of Istio

Cons of Micro

17
Performance

Be the first to leave a con

Sign up to add or upvote consMake informed product decisions

566

2.7K

296

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 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 and Micro as a desired skillset

Staff Software Engineer, Configuration Management

San Francisco, CA, US; , US

View Job Details

+10

Backend Agent Engineer, Observability

Postman

, United States

View Job Details

See jobs for Istio

See jobs for Micro

What companies use Istio?

What companies use Micro?

Manage your open source components, licenses, and vulnerabilities

Learn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Istio?

What tools integrate with Micro?

No integrations found

Sign up to get full access to all the tool integrationsMake informed product decisions

What are some alternatives to Istio 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.

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.

See all alternatives

Istio vs Micro

Need advice about which tool to choose?Ask the StackShare community!

Pros of Istio

Pros of Micro

Sign up to add or upvote prosMake informed product decisions

Cons of Istio

Cons of Micro

Sign up to add or upvote consMake informed product decisions

What is Istio?

What is Micro?

Need advice about which tool to choose?Ask the StackShare community!

What companies use Istio?

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 Micro?

Sign up to get full access to all the tool integrationsMake informed product decisions

Related Comparisons

Trending Comparisons

Top Comparisons