Microsoft IIS vs Undertow: What are the differences?
Developers describe Microsoft IIS 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. On the other hand, Undertow is detailed as "A flexible performant web server written in java". It is a flexible performant web server written in java, providing both blocking and non-blocking API’s based on NIO. It has a composition based architecture that allows you to build a web server by combining small single purpose handlers. The gives you the flexibility to choose between a full Java EE servlet 4.0 container, or a low level non-blocking handler, to anything in between.
Microsoft IIS and Undertow belong to "Web Servers" category of the tech stack.
Microsoft, MIT, and Starbucks are some of the popular companies that use Microsoft IIS, whereas Undertow is used by CurrencyFair, Notify-e, and Kreomi. Microsoft IIS has a broader approval, being mentioned in 1935 company stacks & 2036 developers stacks; compared to Undertow, which is listed in 8 company stacks and 5 developer stacks.
What is Microsoft IIS?
What is Undertow?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Undertow?
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Microsoft IIS?
What are the cons of using Undertow?
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.
Web server for our 9 web applications and associated web services and external integrations