Need advice about which tool to choose?Ask the StackShare community!
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
Pros of Apache Traffic 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
Sign up to add or upvote prosMake informed product decisions
Cons of Apache Traffic Server
Cons of NGINX
- Advanced features require subscription8
Sign up to add or upvote consMake informed product decisions
What is Apache Traffic Server?
What is NGINX?
Need advice about which tool to choose?Ask the StackShare community!
What companies use Apache Traffic Server?
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
Blog Posts
+12
+17
+22
+31+46+15
+6+9