Istio vs nginx: What are the differences?
What is 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.
What is nginx? A high performance free open source web server powering busiest sites on the Internet. nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018.
Istio belongs to "Microservices Tools" category of the tech stack, while nginx can be primarily classified under "Web Servers".
"Zero code for logging and monitoring" is the top reason why over 4 developers like Istio, while over 1437 developers mention "High-performance http server" as the leading cause for choosing nginx.
Istio and nginx are both open source tools. It seems that Istio with 18.9K GitHub stars and 3.21K forks on GitHub has more adoption than nginx with 9.31K GitHub stars and 3.5K GitHub forks.
Airbnb, Uber Technologies, and Spotify are some of the popular companies that use nginx, whereas Istio is used by Entelo, Cuemby, and AgFlow. nginx has a broader approval, being mentioned in 10607 company stacks & 12951 developers stacks; compared to Istio, which is listed in 51 company stacks and 116 developer stacks.
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.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Istio?
What is NGINX?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions