Why should you care?

You care about this when more than one developer touches ShopNest and you need safe merges and automatic test-and-deploy pipelines.

See it live — copy this example

Create a Web API project (dotnet new webapi), paste the code, then run dotnet run.

# Azure App Service or AKS
az webapp deploy --resource-group shopnest-rg --name order-api --src-path ./publish.zip

Run Example »

This lesson uses terminal or setup steps. Run commands on your computer — the live editor appears on coding lessons.

What happened?

• The example shows IIS and Azure Deployment wired into User Service.
• Read each line, run it locally, then change one setting and observe what breaks or improves.
• That is how teams learn in production too — small experiments, not big bang rewrites.

Try it yourself

1. Open or create the ShopNest project area for User Service.
2. Apply the IIS and Azure Deployment pattern from the lesson example.
3. Run dotnet build && dotnet run (or docker compose up when the lesson uses containers).
4. Change a string or route in the example and save — watch Swagger or the RabbitMQ Management UI update.
5. Break the code on purpose (remove a semicolon), read the error message, then fix it.

Remember

IIS and Azure Deployment connects to User Service in ShopNest Cloud-Native. Practice by editing the example yourself — do not only read. Move on when you can explain this topic in your own words without looking.

Real-world: HDFC-style fund transfer

Transfer, ledger, fraud check, and SMS run as separate services with idempotency keys. Saga compensates if fraud blocks after debit.

Outcome: Salary-day load handled without duplicate debits or shared-database locks.