Why should you care?

You use this to build portfolio proof — a full vertical slice you can demo, deploy, and explain in interviews.

See it live — copy this example

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

// ShopNest PaymentService — capstone module
// 1. Gateway + JWT  2. Order→Payment saga  3. RabbitMQ
// 4. docker compose up  5. Grafana dashboard
// README: architecture diagram + demo URL

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 Payment Gateway System wired into Payment 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 Payment Service.
2. Apply the Payment Gateway System 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 number in the example and run again — predict the output first.
5. Break the code on purpose (remove a semicolon), read the compiler error, then fix it.

Remember

Payment Gateway System connects to Payment 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: ShopNest Cloud-Native capstone

Eight services, YARP gateway, RabbitMQ, Docker Compose locally, AKS in production, OpenTelemetry traces on every checkout.

Outcome: Portfolio-ready proof you can demo in interviews and on your resume.