Need advice about which tool to choose?Ask the StackShare community!
nginx vs Traefik: What are the differences?
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; Traefik: Load Balancer for Microservices. Træfɪk is a modern HTTP reverse proxy and load balancer made to deploy microservices with ease. It supports several backends (Docker, Swarm, Mesos/Marathon, Kubernetes, Consul, Etcd, Zookeeper, BoltDB, Rest API, file...) to manage its configuration automatically and dynamically.
nginx and Traefik are primarily classified as "Web Servers" and "Load Balancer / Reverse Proxy" tools respectively.
"High-performance http server" is the top reason why over 1437 developers like nginx, while over 10 developers mention "Kubernetes integration" as the leading cause for choosing Traefik.
nginx and Traefik are both open source tools. It seems that Traefik with 23.2K GitHub stars and 2.4K forks on GitHub has more adoption than nginx with 9.11K GitHub stars and 3.44K GitHub forks.
Airbnb, Uber Technologies, and Spotify are some of the popular companies that use nginx, whereas Traefik is used by Docplanner, Viadeo, and Condé Nast. nginx has a broader approval, being mentioned in 8676 company stacks & 2560 developers stacks; compared to Traefik, which is listed in 47 company stacks and 20 developer stacks.
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!
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.
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."
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.
I use nginx because its more flexible and easy to configure
I use Apache HTTP Server because it's intuitive, comprehensive, well-documented, and just works
We use Traefik as the web server.
The reasons for choosing Traefik over Nginx are as follows:
- Traefik built-in Let’s Encrypt and supports automatic renewal
- Traefik automatically enables HTTP/2
- Prometheus can be supported through simple Traefik configuration
- cookiecutter django integrates Traefik's configuration by default
We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.
We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job
The biggest win for naologic was the ability to set dynamic configurations without having to restart the server
Pros of NGINX
- High-performance http server1.4K
- Performance894
- Easy to configure729
- Open source607
- Load balancer530
- Free288
- Scalability288
- Web server224
- Simplicity175
- Easy setup136
- Content caching30
- Web Accelerator21
- Capability15
- Fast14
- Predictability12
- High-latency12
- Reverse Proxy8
- The best of them7
- Supports http/27
- Enterprise version5
- Great Community5
- Lots of Modules5
- High perfomance proxy server4
- Streaming media delivery3
- Reversy Proxy3
- Streaming media3
- Embedded Lua scripting3
- GRPC-Web2
- Blash2
- Lightweight2
- Fast and easy to set up2
- Slim2
- saltstack2
- Virtual hosting1
- Narrow focus. Easy to configure. Fast1
- Along with Redis Cache its the Most superior1
- Ingress controller1
Pros of Traefik
- Kubernetes integration20
- Watch service discovery updates18
- Letsencrypt support14
- Swarm integration13
- Several backends12
- Ready-to-use dashboard6
- Easy setup4
- Rancher integration4
- Mesos integration1
- Mantl integration1
Sign up to add or upvote prosMake informed product decisions
Cons of NGINX
- Advanced features require subscription8
Cons of Traefik
- Not very performant (fast)7
- Complicated setup7
Sign up to add or upvote consMake informed product decisions
What is NGINX?
What is Traefik?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Traefik?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Traefik?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+12
+17
+22
+31+46+15
+6+9