Need advice about which tool to choose?Ask the StackShare community!
Gunicorn vs nginx: What are the differences?
What is Gunicorn? A Python WSGI HTTP Server for UNIX. Gunicorn is a pre-fork worker model ported from Ruby's Unicorn project. The Gunicorn server is broadly compatible with various web frameworks, simply implemented, light on server resources, and fairly speedy.
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.
Gunicorn and nginx can be categorized as "Web Servers" tools.
"Python" is the top reason why over 26 developers like Gunicorn, while over 1437 developers mention "High-performance http server" as the leading cause for choosing nginx.
Gunicorn and nginx are both open source tools. nginx with 9.1K GitHub stars and 3.43K forks on GitHub appears to be more popular than Gunicorn with 5.96K GitHub stars and 1.12K GitHub forks.
According to the StackShare community, nginx has a broader approval, being mentioned in 8669 company stacks & 2556 developers stacks; compared to Gunicorn, which is listed in 184 company stacks and 51 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
For us, NGINX is a lite HTTP server easy to configure. On our research, we found a well-documented software we a lot of support from the community.
We have been using it alongside tools like certbot and it has been a total success.
We can easily configure our sites and have a folder for available vs enabled sites, and with the nginx -t command we can easily check everything is running fine.
- Server rendered HTML output from PHP is being migrated to the client as Vue.js components, future plans to provide additional content, and other new miscellaneous features all result in a substantial increase of static files needing to be served from the server. NGINX has better performance than Apache for serving static content.
- The change to NGINX will require switching from PHP to PHP-FPM resulting in a distributed architecture with a higher complexity configuration, but this is outweighed by PHP-FPM being faster than PHP for processing requests.
- The NGINX + PHP-FPM setup now allows for horizontally scaling of resources rather vertically scaling the previously combined Apache + PHP resources.
- PHP shell tasks can now efficiently be decoupled from the application reducing main application footprint and allow for scaling of tasks on an individual basis.
Pros of Gunicorn
- Python34
- Easy setup30
- Reliable8
- Light3
- Fast3
Pros of NGINX
- High-performance http server1.4K
- Performance893
- Easy to configure729
- Open source607
- Load balancer530
- Free288
- Scalability288
- Web server225
- Simplicity175
- Easy setup136
- Content caching30
- Web Accelerator21
- Capability15
- Fast14
- High-latency12
- Predictability12
- Reverse Proxy8
- The best of them7
- Supports http/27
- Great Community5
- Lots of Modules5
- Enterprise version5
- High perfomance proxy server4
- Reversy Proxy3
- Streaming media delivery3
- 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
Sign up to add or upvote prosMake informed product decisions
Cons of Gunicorn
Cons of NGINX
- Advanced features require subscription9
Sign up to add or upvote consMake informed product decisions
What is Gunicorn?
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
What tools integrate with Gunicorn?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+12
+17
+22
+31+46+15
+6+9