Istio vs NGINX

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

Istio

663
1.2K
+ 1
44
NGINX

95.2K
45.4K
+ 1
5.5K
Add tool

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.

Advice on Istio and NGINX

I am diving into web development, both front and back end. I feel comfortable with administration, scripting and moderate coding in bash, Python and C++, but I am also a Windows fan (i love inner conflict). What are the votes on web servers? IIS is expensive and restrictive (has Windows adoption of open source changed this?) Apache has the history but seems to be at the root of most of my Infosec issues, and I know nothing about nginx (is it too new to rely on?). And no, I don't know what I want to do on the web explicitly, but hosting and data storage (both cloud and tape) are possibilities. Ready, aim fire!

See more
Replies (1)
Simon Aronsson
Developer Advocate at k6 / Load Impact · | 4 upvotes · 252.6K views
Recommends
NGINXNGINX

I would pick nginx over both IIS and Apace HTTP Server any day. Combine it with docker, and as you grow maybe even traefik, and you'll have a really flexible solution for serving http content where you can take sites and projects up and down without effort, easily move it between systems and dont have to handle any dependencies on your actual local machine.

See more
Needs advice
on
Apache HTTP ServerApache HTTP Server
and
NGINXNGINX

From a StackShare Community member: "We are a LAMP shop currently focused on improving web performance for our customers. We have made many front-end optimizations and now we are considering replacing Apache with nginx. I was wondering if others saw a noticeable performance gain or any other benefits by switching."

See more
Replies (3)
Recommends
NGINXNGINX

I use nginx because it is very light weight. Where Apache tries to include everything in the web server, nginx opts to have external programs/facilities take care of that so the web server can focus on efficiently serving web pages. While this can seem inefficient, it limits the number of new bugs found in the web server, which is the element that faces the client most directly.

See more
Leandro Barral
Recommends
NGINXNGINX

I use nginx because its more flexible and easy to configure

See more
Christian Cwienk
Software Developer at SAP · | 1 upvotes · 239.7K views

I use Apache HTTP Server because it's intuitive, comprehensive, well-documented, and just works

See more
Decisions about Istio and NGINX
Prateek Mittal
Fullstack Engineer| Ruby | React JS | gRPC at Ex Bookmyshow | Furlenco | Shopmatic · | 4 upvotes · 157.1K views

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.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Istio
Pros of NGINX
  • 13
    Zero code for logging and monitoring
  • 8
    Service Mesh
  • 7
    Great flexibility
  • 4
    Ingress controller
  • 3
    Resiliency
  • 3
    Easy integration with Kubernetes and Docker
  • 3
    Full Security
  • 3
    Powerful authorization mechanisms
  • 1.4K
    High-performance http server
  • 896
    Performance
  • 728
    Easy to configure
  • 606
    Open source
  • 529
    Load balancer
  • 286
    Scalability
  • 285
    Free
  • 222
    Web server
  • 173
    Simplicity
  • 134
    Easy setup
  • 29
    Content caching
  • 19
    Web Accelerator
  • 14
    Capability
  • 13
    Fast
  • 11
    Predictability
  • 10
    High-latency
  • 7
    Reverse Proxy
  • 6
    Supports http/2
  • 4
    The best of them
  • 4
    Lots of Modules
  • 4
    Enterprise version
  • 4
    Great Community
  • 3
    High perfomance proxy server
  • 3
    Streaming media
  • 3
    Embedded Lua scripting
  • 3
    Reversy Proxy
  • 3
    Streaming media delivery
  • 2
    Fast and easy to set up
  • 2
    Lightweight
  • 2
    Slim
  • 2
    saltstack
  • 1
    Virtual hosting
  • 1
    Blash
  • 1
    GRPC-Web
  • 1
    Ingress controller
  • 1
    Narrow focus. Easy to configure. Fast
  • 1
    Along with Redis Cache its the Most superior
  • 0
    A

Sign up to add or upvote prosMake informed product decisions

Cons of Istio
Cons of NGINX
  • 13
    Performance
  • 8
    Advanced features require subscription

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

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.

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

What companies use Istio?
What companies use NGINX?
See which teams inside your own company are using Istio or NGINX.
Sign up for Private StackShareLearn More

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

What tools integrate with Istio?
What tools integrate with NGINX?

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

Blog Posts

What are some alternatives to Istio and NGINX?
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