GlassFish vs Microsoft IIS: What are the differences?
Developers describe GlassFish as "The Open Source Java EE Reference Implementation". 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. On the other hand, Microsoft IIS is detailed as "A web server for Microsoft Windows". 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.
GlassFish and Microsoft IIS can be categorized as "Web Servers" tools.
According to the StackShare community, Microsoft IIS has a broader approval, being mentioned in 1935 company stacks & 2036 developers stacks; compared to GlassFish, which is listed in 5 company stacks and 4 developer stacks.
What is GlassFish?
What is Microsoft IIS?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose GlassFish?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using GlassFish?
What are the cons of using Microsoft IIS?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
This is a legacy system requirement. We have some portions of our website written in PHP. Normally this wouldn't be an issue but at the time they decided to use PHP+Windows they were also trying to use MSSQL databases (All the microsoft influence was due to some azure credits the company received early on). The particular driver they ended up picking forced them into using the
mssql_* functions instead of PDO. This meant that the majority of the site used these rather outdated calls and replacing them was a rather large endeavour. So while we migrate some of the PHP backend away to various node.js api systems we are simply sustaining the existing PHP portions.
J2EE application server to handle JDBC connection pooling, shared SDK, JDNI resources, etc. and host our JVM-based web applications (primarily Rails via JRuby).
Web server for our 9 web applications and associated web services and external integrations