Layer 1 · Session 1 · Implemented
Course orientation and the evolving workload
Cloud engineering means making a workload deployable, secure, observable, repeatable, resilient, and operable, not memorizing products.
The system, not the checklist
A document enters a small ASP.NET Core workload, metadata is recorded, background work processes it, and a health endpoint reports readiness. Azure services replace local substitutes over time.
Learning objectives
- Connect the workload to the curriculum.
- Locate app, tests, infrastructure, scripts, labs, and decisions.
- Run locally and verify health.
- Interpret course status.
Prediction
Reveal
Repository map
src/ workload · tests/ checks · infrastructure/ Bicep · scripts/ lifecycle · architecture/ decisions · course-status.json stateGuided walkthrough
Confirm SDK
dotnet --infoWhy and effect: Reads SDK/runtime information.
Verify: An 8.x SDK appears.
Undo: Nothing.
Cost: No Azure charges.
Build and test
dotnet restore
dotnet build --no-restore
dotnet test --no-buildWhy and effect: Restores packages, compiles, and tests locally.
Verify: All exit 0.
Undo: Delete bin/obj if desired.
Cost: No Azure charges.
Run workload
dotnet run --project .\src\CloudJourney.WebWhy and effect: Starts locally, not in Azure.
Verify: Home loads and /health returns Healthy.
Undo: Ctrl+C.
Cost: No Azure charges.
Verification and troubleshooting
- Home loads.
- /health returns 200.
- A sample document appears.
- Tests pass.
dotnet not recognized
Knowledge check
Architecture delta
Added local process, storage, health, logs, and tests. You own everything; local success does not prove production readiness.