Need advice about which tool to choose?Ask the StackShare community!
Undertow vs nginx: What are the differences?
- The Architecture: Undertow is a lightweight web server that is built around a non-blocking I/O model, allowing it to efficiently handle thousands of concurrent connections with very low resource consumption. On the other hand, Nginx is also designed to handle a large number of simultaneous connections, but it uses an event-driven architecture that relies on asynchronous and event-driven processing, allowing it to efficiently serve static files and act as a reverse proxy for load balancing and caching.
- Configuration and Extensibility: Undertow uses a configuration file in XML format to define its settings and deployments, making it customizable and easy to manage. Nginx, on the other hand, uses a simple and readable configuration file written in its own scripting language that provides flexibility and extensibility to customize its behavior and integrate with other systems.
- SSL/TLS Support: Both Undertow and Nginx provide support for SSL/TLS encryption protocols to secure web communications. However, Nginx has built-in capabilities to handle SSL/TLS termination and certificate management, making it more suitable for handling HTTPS traffic without the need for additional components or configurations.
- HTTP/2 Support: Nginx has better native support for the HTTP/2 protocol, which brings significant performance improvements over the older HTTP/1.1 protocol. By contrast, Undertow requires additional configuration and modules to support HTTP/2, which may require more effort and expertise to set up and optimize.
- Embedded Mode: Undertow can be embedded within Java applications, allowing developers to create lightweight and self-contained web servers as part of their application deployments. On the other hand, Nginx is typically used as a standalone web server or a reverse proxy and does not have built-in capabilities for embedding within applications.
- Operating System Support: Nginx is a cross-platform web server that can run on a wide range of operating systems, including Windows, Linux, macOS, and various Unix flavors. Meanwhile, Undertow is primarily tailored for Java applications and is supported on Java Virtual Machines (JVMs) running on different platforms.
In summary, Undertow is a lightweight Java-based web server that excels in terms of performance and resource efficiency, while Nginx offers a versatile and highly customizable solution with better support for SSL/TLS, HTTP/2, and operating system diversity.
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 NGINX
- High-performance http server1.4K
- Performance894
- Easy to configure730
- Open source607
- Load balancer530
- Free289
- Scalability288
- Web server226
- Simplicity175
- Easy setup136
- Content caching30
- Web Accelerator21
- Capability15
- Fast14
- High-latency12
- Predictability12
- Reverse Proxy8
- Supports http/27
- The best of them7
- Great Community5
- Lots of Modules5
- Enterprise version5
- High perfomance proxy server4
- Embedded Lua scripting3
- Streaming media delivery3
- Streaming media3
- Reversy Proxy3
- Blash2
- GRPC-Web2
- 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 Undertow
- Performance4
- Lower footprint1
Sign up to add or upvote prosMake informed product decisions
Cons of NGINX
- Advanced features require subscription10
Cons of Undertow
- Smaller community1
- Less known1