Why should you care?

You care about this when one business action spans Order, Payment, and Inventory — and you cannot use one SQL transaction across three databases.

See it live — copy this example

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

// No 2PC across OrderDb + PaymentDb
// Order status = Paid; Inventory may show Reserved 200ms later — UI handles lag

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 Distributed Transactions wired into Notification 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 Notification Service.
2. Apply the Distributed Transactions 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

Distributed Transactions connects to Notification 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: Zoho-style SaaS billing

Billing, tenant provisioning, and feature flags are separate services. A billing fix deploys without redeploying the entire admin UI backend.

Outcome: Multi-tenant isolation and faster team velocity on subscription changes.