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.

public class PlaceOrderStateMachine : MassTransitStateMachine<PlaceOrderState>
{
    public State AwaitingPayment { get; private set; }
    // PaymentSucceeded → ReserveInventory → Completed
    // PaymentFailed → Compensate (cancel order)
}

Run Example »

Edit the code and click Run — like W3Schools Try it Yourself.

What happened?

• The example shows Choreography Saga wired into Analytics 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 Analytics Service.
2. Apply the Choreography Saga 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

Choreography Saga connects to Analytics 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.