Microsoft IIS

Publishing applications or websites is easy with Microsoft IIS. You don't need external software or complicated tutorials involving command lines and editing configuration files.

On other hand, sometimes the troubleshooter needs a high knowledge of Windows Server, Registry, and tools to debug the application. If you need to host non-Microsoft technology as PHP pages or have a low budget, I recommend IIS equivalent software as Apache.

IIS as a web application server is perfectly suited for .net, .net core, asp.net applications. Our core ESB runs on IIS and has hundreds of gigabytes of data moved through it every day spread across millions of transactions. We have other mission critical applications that deliver our results to patients and doctors relying on IIS web application servers. If you stay in the Microsoft development stack, IIS is a top tier, efficient, and reliable web server.

Depending on your needs a company, Microsoft IIS may or may not be a great solution. In the case of my company, we do not have a ton of security protocols to go through like some other companies. Take for example, a government agency or maybe health care, which has numerous data privacy restrictions that need to be considered.

Microsoft IIS is great for easily serving up web applications! Any developer can easily write a quick web based app and deploy it for end users to access with a few clicks of a button as long as they have the access they need! Since developers have access to dev environments/servers, they can easily deploy their apps and test everything and configure it based on the needs of the application and just provide the configuration file once ready for production use.

IIS can, however, be a little difficult to use for new developers. It has many configurations, but easy to find the documentation.

We found it most suited for hosting our lightweight internal monitoring sites. The host environment easily handles the load and the websites are able to be maintained and hosted with little fuss. Familiarity with the software is required to do anything complicated but once you get the hang of it, it becomes a straight forward tool for hosting.

Microsoft IIS is well suited if you already have the expensive Windows Server infrastructure--it will already be on there, most likely (or not very hard to get on if it isn't). If you are going to serve static sites or some kind of .NET (including Core) application, it is the obvious choice. If you are going to serve a PHP or Node.JS application behind it, I wouldn't--I'd recommend getting all the better and free tools like Linux, NGINX, Apache, etc. to do that for you--you'll save money and time.

I consider IIS a good solution when you have to publish internal web applications, but I feel to suggest to use other system, for security reason,if you need to go outside your organization.

[Microsoft IIS is] well suited for any scenario... I can't imagine a scenario where it's not suited. Compared to apache of any other server, IIS is what this kind of application is supposed to do: be simple! Of course, there might be scenario's where you want a leaner or modular product with a web server that works for just one application, but in my opinion that is never an advantage, since a centrally managed application is always faster to use, and speed is, in the end, the only thing that matters in IT.

We have used IIS to host our applications for decades and we are very happy with it. One thing we have used IIS for is as a reverse proxy server. All of our external traffic runs through it and it acts as an added layer of security and obfuscation from external attacks. We are also able to finely control traffic through the server.

Microsoft IIS is great for Intranet, where all users are on Windows and they require access to web sites that can be controlled by Active Directory groups.

It goes without saying that it is well suited to hosting websites built on a Microsoft technology stack, but we also have a couple of PHP websites running using the plugin that run very well.

Well suited for small websites which need to be hosted on the same environment without getting into the trouble of managing services differently. Clustering is a costly offense if you want to deal with a high volume of data, because of IIS' costly licensing for the server, and the OS also makes it less favorable.

I would recommend it if you use a Windows environment and have to utilize a medium processing load. If you have high availability loads, I'd recommend a more simplified webserver like Nginix or Apache. They provide a better threading model for resources.

Microsoft IIS is perfect for spinning up a new website. You can manually set everything up or create scripts to automate the process. Microsoft IIS also works great with Microsoft Azure DevOps continuous Integration and deployment services. This makes Microsoft IIS a powerful tool for hosting as you can automate every aspect of deployment.

Microsoft IIS is suitable for those that work with .NET applications and other Microsoft technologies.

Microsoft IIS is well suited for simple website hosting and for more complex web application setups as well. Granular security features allow you to make your web site or app to be protected as much as possible. Plus by default the best integration with other Microsoft services like Active Directory, WSUS, SCCM, etc. However, if you need just a basic website that is not based on MS components, open source solutions like Apache or Nginx could be better and cheaper (based on Linux).

Well suited when utilizing Windows servers that require multiple sites to be deployed and you don't want to employ multiple services to run different applications

For multiple applications, IIS is the best suitable software. Comes with Windows (if you install a patch file). Easy to install. Navigation is so simple that a mid level programmer can understand. Supports almost all the Webservers. Managing the websites and the applications is so simple. When hosting the application it takes its default port number instead of specifying.

IIS is excellent for integrating web resources for existing Microsoft products, especially Exchange. It is formidable at deploying applications, especially for internal use.

For all .Net based web applications on a Windows server infrastructure, IIS is the first choice. For bundled, third-party apps, it usually makes more sense to use the web server the app comes with (Apache, etc).

It is perfect for small dev projects where you would like to put the data into SQL. Put IIS together with SQL Express and you have a fairly robust application space for free! If you are passing along a big data site I don't think that IIS would be your best bet. It does offer clustering, which is the IIS answer to high volume, but that can get pricey with multiple server instances and licensing for the OS.

In my opinion IIS is far more appropriate with internal web applications ONLY because the alternative UNIX equivalents feel more secure by nature when working with public facing resources.

Many commercial off-the-shelf (COTS) vendors only support Microsoft IIS, in these cases I would not recommend trying to make it work with other platforms such as Apache. If you are in a primarily Microsoft Windows Server environment, I would recommend using Microsoft IIS as opposed to trying to make Apache or other web platforms run on Windows. If you have an abundance of Linux knowledge in-house and the application supports Apache, I recommend using Apache on Linux as a more optimal use of resources.

Microsoft IIS is less suited for running a few generic websites as the resources consumed are more than some of the open source servers. However, when it comes to dynamic web applications Microsoft IIS shines.

Having used Microsoft IIS with most languages and database platforms, I would not hesitate to recommend it for any organizations with a strong Microsoft background.