Microsoft IIS

We have a couple of legacy applications that have backend written in .NET Core & frontend in Angular. Due to the .NET Core part, as well as some other reasons, it was decided that the applications would be hosted on Windows Server VMs, both frontend & backend.

It means we use Microsoft IIS to host the frontend, with redirect routes for backend API calls.

• Virtually zero effort required to setup on Windows Server
• Dev env can get up & running very quickly
• Windows GUI makes things much easier for beginners

Apache Tomcat and Apache HTTP Server

Apache HTTP Server, Apache Tomcat, Amazon CloudFront

Hosting websites on-premises or in the cloud, Microsoft IIS is the best choice for deploying websites using Microsoft technology such as asp.net pages. In our company, we have developed some systems for our customers, such as access control, timesheet, and hotel checkin/out, among others; the simplicity to automatically create and configure a website is a differential of the solution, because the end user is not always an IT technician with the necessary knowledge to install and configure a web application, that's why the "NNF" configuration (Next-Next- Finish) is a big differentiator. However, Microsoft IIS has great features for advanced users, allowing for example, to host several sites on the same server and segregate them for internal publication such as on an intranet, as well as for external publication on the Internet.

With constant evolution, security requirements and compatibility with new technologies are implemented in each version; and the availability of extensions allows hosting of non-Microsoft content such as PHP pages and Node.

• Native support to Microsoft technology as aspnet and framework content
• Licensing costs including as part of the operation system
• More easy to maintain and administer if compared to concurrency
• Application Setup provided by the team of developer,s does all the configuration and parameterization of the sites, with minimal user interaction

• Positive: Easy installation
• Positive: Compatibility with many technologies (native or by add-on extensions)
• Positive: No software or license costs for Windows operation systems
• Negative: Complicated to use third-party authentication or open source patterns such as OPENID
• Negative: Use more hardware resources than competing systems

Apache Ant and Apache Tomcat

Microsoft SQL Server, ASP.NET, Oracle Database

• Integration to Azure devops for CICD
• Reliability
• Performance
• Scalability

• Since IIS is relatively easy to setup and maintain it reduces operational costs.
• Security patches come down as part of routine Microsoft updates, so keeping up to date is easy.
• Integration with Azure devops means deploying applications is rolled out via CICD very easy to manage.

Apache HTTP Server and NGINX

Visual Studio IDE, Azure DevOps Services (formerly VSTS), Azure SQL Database, Microsoft Azure Active Directory, Microsoft Power Automate (formerly Microsoft Flow), Azure Blob Storage, Azure App Service, Azure API Management

• Remote management.
• Scalable web infrastructure.
• Diagnostic tools.

• It has reduced our cost a bit in terms of head count
• The scalability has been nice to keep up with user demand
• The access protection has been a nice benefit

Apache HTTP Server

Oracle WebLogic Application Server, Apache Kafka, Red Hat JBoss Data Virtualization

• Readily available.
• Works on our required machines.
• Does what it needs to with regards to hosting.

• Allowing us to internally host our monitoring websites allows quick access to data that can be quite hidden, saving developer time.
• It was inexpensive compared to more bulky solutions saving upfront cost.
• It’s easy to install and enable allowing more developer savings.