Go Micro vs Istio

Overview

Istio

Stacks2.3K

Followers1.5K

Votes54

GitHub Stars37.6K

Forks8.1K

Go Micro

Stacks20

Followers47

Votes0

GitHub Stars22.6K

Forks2.4K

Go Micro vs Istio: What are the differences?

Service Mesh Implementation: Go Micro is a framework for distributed systems development that can be used with any service mesh implementation, while Istio is a comprehensive service mesh platform that includes features like traffic management, security, and observability out of the box.
Routing and Load Balancing: Istio offers advanced routing capabilities and traffic management features such as weighted routing, fault injection, and circuit breaking, while Go Micro focuses on simplifying the process of building distributed systems without providing as extensive routing and load balancing features.
Security and Authorization: Istio has built-in security features like mutual TLS authentication, access control policies, and end-to-end encryption, ensuring secure communication between services, whereas Go Micro relies on the underlying service mesh implementation for security capabilities.
Observability and Monitoring: Istio provides robust observability tools such as metrics collection, distributed tracing, and service monitoring through integration with tools like Prometheus and Grafana, enabling detailed insights into service communication and performance, which Go Micro may lack in its core functionalities.
Configuration and Traffic Control: Istio allows fine-grained control over configuration with features like traffic shifting, URL rewriting, and header manipulation, empowering users to customize how traffic flows between services, whereas Go Micro may offer basic configuration options but lacks the intricate traffic control capabilities provided by Istio.
Ecosystem Integration: Istio has a strong ecosystem with integrations into popular tools like Kubernetes, Prometheus, and Jaeger, facilitating seamless adoption in modern cloud-native environments, while Go Micro, being a more lightweight framework, may not have the same level of integrations and ecosystem support out of the box.

In Summary, Go Micro is a lightweight framework for building distributed systems, while Istio is a feature-rich service mesh platform with advanced capabilities for managing and securing microservices architectures.

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)

Manual

Advice on Istio, Go Micro

Prateek

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

lyc218

Feb 21, 2020

Needs advice

Envoy proxy is widely adopted in many companies for service mesh proxy, but it utilizes BoringSSL by default. Red Hat OpenShift fork envoy branch with their own OpenSSL support, I wonder any other companies are also using envoy-openssl branch for compatibility? How about AWS App Mesh?

Any input would be much appreciated!

42.7k views42.7k

Comments

Detailed Comparison

Istio	Go Micro
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.	It provides the core requirements for distributed systems development including RPC and Event driven communication. The micro philosophy is sane defaults with a pluggable architecture. We provide defaults to get you started quickly but everything can be easily swapped out.
-	Service Discovery; Load Balancing; Message Encoding; Async Messaging; Pluggable Interfaces
Statistics
GitHub Stars 37.6K	GitHub Stars 22.6K
GitHub Forks 8.1K	GitHub Forks 2.4K
Stacks 2.3K	Stacks 20
Followers 1.5K	Followers 47
Votes 54	Votes 0
Pros & Cons
Pros 14 Zero code for logging and monitoring 9 Service Mesh 8 Great flexibility 5 Powerful authorization mechanisms 5 Ingress controller Cons 17 Performance	No community feedback yet
Integrations
Kubernetes Docker	Kubernetes Golang

What are some alternatives to Istio, Go Micro ?

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.

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.

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

Related Comparisons

Go Micro vs Istio: What are the differences?

Service Mesh Implementation: Go Micro is a framework for distributed systems development that can be used with any service mesh implementation, while Istio is a comprehensive service mesh platform that includes features like traffic management, security, and observability out of the box.
Routing and Load Balancing: Istio offers advanced routing capabilities and traffic management features such as weighted routing, fault injection, and circuit breaking, while Go Micro focuses on simplifying the process of building distributed systems without providing as extensive routing and load balancing features.
Security and Authorization: Istio has built-in security features like mutual TLS authentication, access control policies, and end-to-end encryption, ensuring secure communication between services, whereas Go Micro relies on the underlying service mesh implementation for security capabilities.
Observability and Monitoring: Istio provides robust observability tools such as metrics collection, distributed tracing, and service monitoring through integration with tools like Prometheus and Grafana, enabling detailed insights into service communication and performance, which Go Micro may lack in its core functionalities.
Configuration and Traffic Control: Istio allows fine-grained control over configuration with features like traffic shifting, URL rewriting, and header manipulation, empowering users to customize how traffic flows between services, whereas Go Micro may offer basic configuration options but lacks the intricate traffic control capabilities provided by Istio.
Ecosystem Integration: Istio has a strong ecosystem with integrations into popular tools like Kubernetes, Prometheus, and Jaeger, facilitating seamless adoption in modern cloud-native environments, while Go Micro, being a more lightweight framework, may not have the same level of integrations and ecosystem support out of the box.

Go Micro vs Istio

Overview