StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Platform as a Service
  4. Web Servers
  5. GlassFish vs nginx

GlassFish vs nginx

OverviewDecisionsComparisonAlternatives

Overview

NGINX
NGINX
Stacks115.0K
Followers61.9K
Votes5.5K
GitHub Stars28.4K
Forks7.6K
GlassFish
GlassFish
Stacks581
Followers112
Votes0

GlassFish vs nginx: What are the differences?

  1. Scalability: GlassFish is primarily designed for Java EE applications and offers extensive support for Java technologies, making it ideal for large enterprise applications requiring complex configurations. On the other hand, nginx is a lightweight web server and proxy server that excels in serving static content and handling a high volume of concurrent connections efficiently.
  2. Configuration: GlassFish typically requires more complex configuration due to its comprehensive support for Java EE components and applications, with various XML deployment descriptors and settings to manage. In contrast, nginx has a simple and intuitive configuration syntax that is easy to understand and manage, allowing for quick setup and deployment of web servers with minimal overhead.
  3. Resource Usage: GlassFish is known for its higher resource utilization, especially in memory consumption, as it runs on top of the Java Virtual Machine (JVM) which can be more resource-intensive. nginx, being a lightweight server, is optimized for low resource usage and can efficiently handle a large number of concurrent connections with minimal memory footprint.
  4. Load Balancing: GlassFish provides built-in support for load balancing and clustering features, allowing for the distribution of incoming traffic across multiple server instances for improved performance and fault tolerance. nginx also offers load balancing capabilities through various load-balancing algorithms, making it well-suited for distributing traffic among backend servers in a scalable and efficient manner.
  5. SSL/TLS Termination: nginx is commonly used as a reverse proxy server for SSL/TLS termination, offloading the encryption and decryption process from the backend servers to improve performance and security. GlassFish also supports SSL/TLS encryption for secure communication but may require additional configuration and setup to achieve similar levels of SSL termination functionality.
  6. Community and Support: nginx has a large and active open-source community with extensive documentation, plugins, and community support available, making it easy to find resources and solutions for common issues. GlassFish, while also supported by a community of Java developers, may have less available resources and community support compared to the widespread usage and support for nginx.

In Summary, GlassFish and nginx differ in scalability for enterprise applications, configuration complexity, resource usage efficiency, load balancing capabilities, SSL termination features, and community support and resources.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on NGINX, GlassFish

greg00m
greg00m

Mar 9, 2020

Needs advice

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!

766k views766k
Comments
jlp78
jlp78

May 31, 2019

ReviewonNGINXNGINX

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.

727k views727k
Comments
StackShare
StackShare

May 29, 2019

Needs advice

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."

725k views725k
Comments

Detailed Comparison

NGINX
NGINX
GlassFish
GlassFish

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.

An Application Server means, It can manage Java EE applications You should use GlassFish for Java EE enterprise applications. The need for a seperate Web server is mostly needed in a production environment.

Statistics
GitHub Stars
28.4K
GitHub Stars
-
GitHub Forks
7.6K
GitHub Forks
-
Stacks
115.0K
Stacks
581
Followers
61.9K
Followers
112
Votes
5.5K
Votes
0
Pros & Cons
Pros
  • 1453
    High-performance http server
  • 895
    Performance
  • 730
    Easy to configure
  • 607
    Open source
  • 530
    Load balancer
Cons
  • 10
    Advanced features require subscription
No community feedback yet

What are some alternatives to NGINX, GlassFish?

Apache HTTP Server

Apache HTTP Server

The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet.

Unicorn

Unicorn

Unicorn is an HTTP server for Rack applications designed to only serve fast clients on low-latency, high-bandwidth connections and take advantage of features in Unix/Unix-like kernels. Slow clients should only be served by placing a reverse proxy capable of fully buffering both the the request and response in between Unicorn and slow clients.

Microsoft IIS

Microsoft IIS

Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks.

Apache Tomcat

Apache Tomcat

Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations.

Passenger

Passenger

Phusion Passenger is a web server and application server, designed to be fast, robust and lightweight. It takes a lot of complexity out of deploying web apps, adds powerful enterprise-grade features that are useful in production, and makes administration much easier and less complex.

Gunicorn

Gunicorn

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.

Jetty

Jetty

Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.

lighttpd

lighttpd

lighttpd has a very low memory footprint compared to other webservers and takes care of cpu-load. Its advanced feature-set (FastCGI, CGI, Auth, Output-Compression, URL-Rewriting and many more) make lighttpd the perfect webserver-software for every server that suffers load problems.

Swoole

Swoole

It is an open source high-performance network framework using an event-driven, asynchronous, non-blocking I/O model which makes it scalable and efficient.

Puma

Puma

Unlike other Ruby Webservers, Puma was built for speed and parallelism. Puma is a small library that provides a very fast and concurrent HTTP 1.1 server for Ruby web applications.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase