Overview

Microsoft IIS

Stacks15.5K

Followers7.7K

Votes236

GlassFish

Stacks581

Followers112

Votes0

GlassFish vs Microsoft IIS: What are the differences?

# Key Differences between GlassFish and Microsoft IIS

GlassFish and Microsoft IIS are both popular web servers, but they have key differences that differentiate them in terms of their features and functionalities.

1. **Platform Compatibility**: GlassFish is primarily designed for Java EE applications, making it more suitable for developers who work with Java technologies. On the other hand, Microsoft IIS is a Windows-based web server, making it the go-to choice for developers working in a Microsoft-centric environment.
   
2. **Open Source vs. Proprietary**: GlassFish is an open-source server, providing developers with the flexibility to customize and extend its functionality according to their needs. In contrast, Microsoft IIS is a proprietary server, limiting customization options but offering tight integration with other Microsoft products and technologies.

3. **Scalability**: GlassFish is known for its ability to handle large-scale applications gracefully, with built-in support for clustering and load balancing. Microsoft IIS, while also capable of handling high traffic websites, may require additional configurations and tools to achieve similar levels of scalability.

4. **Security Features**: GlassFish comes with robust security features out of the box, such as support for SSL encryption, role-based access control, and security realms. Microsoft IIS also offers similar security features but may require additional licenses or third-party extensions for advanced security functionalities.

5. **Community Support**: GlassFish benefits from a strong open-source community, providing developers with a wealth of resources, forums, and third-party plugins to enhance its capabilities. Microsoft IIS, on the other hand, relies more on official Microsoft documentation and support channels for assistance and guidance.

6. **Cost Implications**: GlassFish being open-source is free to use, reducing upfront costs for developers and organizations. In contrast, Microsoft IIS typically involves licensing fees, especially for commercial use or advanced features, which may impact the overall cost of a web project.

In Summary, GlassFish and Microsoft IIS differ in platform compatibility, open-source vs. proprietary nature, scalability, security features, community support, and cost implications. Each server has its strengths and weaknesses, catering to different development environments and project requirements.

🔥 Trending in Platform as a Service on StackShare

WordPress Platform As A Service

A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.

Try it View Docs Alternatives

Try

42

41.4k

Advice on Microsoft IIS, GlassFish

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

Detailed Comparison

Microsoft IIS	GlassFish
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.	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
Stacks 15.5K	Stacks 581
Followers 7.7K	Followers 112
Votes 236	Votes 0
Pros & Cons
Pros 83 Great with .net 55 I'm forced to use iis 27 Use nginx 18 Azure integration 15 Best for ms technologyes ms bullshit Cons 1 Hard to set up	No community feedback yet

What are some alternatives to Microsoft IIS, GlassFish?

NGINX

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.

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

Apache Tomcat

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

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

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

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.