Layer 1 · Session 2 · Implemented
Who manages what?
IaaS, PaaS, and SaaS are responsibility models. IIS is web-server software.
Problem and objectives
Put it in Azure is not a design. Decide how much stack you operate.
- Compare service models.
- Separate IIS from IaaS.
- Map one workload across compute options.
- Name control, portability, convenience, and burden.
Teaching simplification: exact boundaries vary by service and configuration.
IIS is not IaaS
IIS is a Windows web server. IaaS is a service model. IIS can run on an Azure VM, where you manage Windows and IIS.
Prediction: App Service fails due to a Windows-only library. Who fixes it?
Reveal
The application team; Azure runs the platform, not application correctness.
Practical inspection
Inspect framework
Select-String -Path .\src\CloudJourney.Web\CloudJourney.Web.csproj -Pattern 'TargetFramework|PackageReference'Why and effect: Exposes runtime assumptions.
Verify: Framework and packages print.
Undo: Nothing.
Cost: No Azure charges.
Inspect configuration
Get-ChildItem .\src\CloudJourney.Web -Filter 'appsettings*.json'Why and effect: Lists configuration files without secrets.
Verify: Expected files appear.
Undo: Nothing.
Cost: No Azure charges.
Cost and cleanup
No Azure resources. Stop local app with Ctrl+C.
Knowledge check
Architecture delta
No component changed. A responsibility, control, and burden decision lens was added.