Need advice about which tool to choose?Ask the StackShare community!
What is Apache HTTP Server?
What is Jetty?
What is nginx?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Apache HTTP Server?
- Web server472
- Fast146
- Ssl support138
Why do developers choose Jetty?
Why do developers choose nginx?
- Performance891
- Open source599
- Scalability286
- Free278
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Apache HTTP Server?
What are the cons of using Jetty?
What are the cons of using nginx?
What companies use Jetty?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Jetty?
Sign up to get full access to all the tool integrationsMake informed product decisions
We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.
Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.
At Kong while building an internal tool, we struggled to route metrics to Prometheus and logs to Logstash without incurring too much latency in our metrics collection.
We replaced nginx with OpenResty on the edge of our tool which allowed us to use the lua-nginx-module to run Lua code that captures metrics and records telemetry data during every request’s log phase. Our code then pushes the metrics to a local aggregator process (written in Go) which in turn exposes them in Prometheus Exposition Format for consumption by Prometheus. This solution reduced the number of components we needed to maintain and is fast thanks to NGINX and LuaJIT.
We used to primarily use nginx for our static web server and proxy in-front of Node.js. Now, we use Caddy. And we couldn't be happier.
Caddy is simpler on all fronts. Configuration is easier. Free HTTPS out of the box. Some fantastic plugins. And for the most part, it's fast.
Don't get me wrong, it's not lost on me that Nginx is actually a superior product.
But for the times when you don't need that extra performance, and complexity - take a look at Caddy.