Why should you care?

You care about this when services leave your laptop and run on servers, Kubernetes, or Azure where restarts and scaling happen automatically.

See it live — copy this example

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

apiVersion: apps/v1
kind: Deployment
metadata:
  name: shopnest-order-api
spec:
  replicas: 3
  template:
    spec:
      containers:
      - name: order-api
        image: shopnest/order-api:1.0.0
        envFrom:
        - secretRef:
            name: order-db-secret

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 Helm Charts wired into Order 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 Order Service.
2. Apply the Helm Charts 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

Helm Charts connects to Order 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: Flipkart Big Billion Day checkout

During peak sales, Order and Payment services scale independently. RabbitMQ buffers spikes so Payment workers catch up without blocking the mobile app.

Outcome: Checkout returns in under 500ms while payment completes in the background — shoppers see clear status updates.