Microsoft IIS vs Passenger: 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, Passenger is detailed as "A fast and robust web server and application server for Ruby, Python and Node.js". 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.
Microsoft IIS and Passenger belong to "Web Servers" category of the tech stack.
"Great with .net" is the top reason why over 77 developers like Microsoft IIS, while over 43 developers mention "Nginx integration" as the leading cause for choosing Passenger.
Passenger is an open source tool with 4.41K GitHub stars and 505 GitHub forks. Here's a link to Passenger's open source repository on GitHub.
According to the StackShare community, Microsoft IIS has a broader approval, being mentioned in 1498 company stacks & 312 developers stacks; compared to Passenger, which is listed in 380 company stacks and 40 developer stacks.
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!
I would pick nginx over both IIS and Apace HTTP Server any day. Combine it with docker, and as you grow maybe even traefik, and you'll have a really flexible solution for serving http content where you can take sites and projects up and down without effort, easily move it between systems and dont have to handle any dependencies on your actual local machine.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Microsoft IIS?
What is Passenger?
Need advice about which tool to choose?Ask the StackShare community!
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
"deploy + forget" application deployment with good default configuration.