Apache Tomcat vs NGINX

• It is very lightweight and not resource intensive, which leads to fast start-up times
• It is very stable, I have not had an outage related to Tomcat in over 10 years and no longer even have support contracts for it.
• It's very scalable, especially in a cloud solution where you can perform auto-scaling and add nodes within short periods of time.

Read full review

• Nginx works really well for serving static files. You can let requests for static files and assets pass directly through to the file system and Nginx will serve them really fast, without touching your web app processes.
• Nginx does a great job with load balancing. You can set up different load balancing strategies, but the default load balancer it comes with out of the box works very well already -- better than any round-robin approach because it checks for availability of the resource before handing off the incoming request.
• Nginx is more memory efficient and generally faster than Apache. It has a small footprint, which can be very helpful, especially if you're running on a VPS.
• Nginx has not crashed on me even once. The robustness of Nginx overall is very impressive.
• You can apply configuration changes to Nginx without needing to restart the server. You can also do reloads of the config without dropping any web requests because Nginx provides a global queue where requests can be held while it reloads the config.

Read full review

• Tomcat is a fairly stable and lightweight application server and it being open source lot of organizations are using it to host their applications.
• I have seen the use of Tomcat decline in recent years because of serverless technical platforms like Lambdas on AWS. Also Spring Boot and Jetty servers can run web applications/APIs by bringing container bundled into the app and without a need for separate server deployment and management. Same is the case with Spring boot, though in Spring Boot you could use embedded Tomcat too. But I have seen developers using Jetty more.

Read full review

• I had some initial problems proxying PHP.
• It’s easy to over complicate your setup.
• Like many applications, some of the error codes can be pretty ambiguous.

Read full review

• The positive impact is its universal support. It's easy to spin up a server and then deploy it to AWS.
• The negative impact is the speed at which development occurs. Relative to a back end built on a scripting language, development time is much slower.
• Overall, it's allowed us to scale the web site as the company grows.

Read full review

• Having such a powerful open source solution allows us a lot of versatility we wouldn’t have otherwise.
• Nginx’s versatility allows us to be really efficient, since we can use one well known tool for multiple solutions.

Read full review