Microsoft IIS - Native Windows Web Server
Use Cases and Deployment Scope
It means we use Microsoft IIS to host the frontend, with redirect routes for backend API calls.
Pros
- Native integration with Windows Server
- Intuitive enough for static web pages hosting
- Good enough URL rewrite rules to support hosting both frontend & backend on the same VM, while avoiding CORS issue at the same time
Cons
- Virtually no infra-as-code support
- Powershell API to automate CI/CD is quite limited
- Troubleshooting is quite cumbersome, with lots of guesswork
Return on Investment
- 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




