Why should you care?

ShopNest cannot use one ACID transaction across Order, Payment, and Inventory services.

See it live — copy this example

Paste into a C# console or class library project and run dotnet run.

public sealed class CheckoutSaga
{
    public async Task RunAsync(string orderId)
    {
        await ReserveStock(orderId);
        try
        {
            await CapturePayment(orderId);
            await Confirm(orderId);
        }
        catch
        {
            await ReleaseStock(orderId); // compensation
            throw;
        }
    }
    Task ReserveStock(string id) { Console.WriteLine($"reserve {id}"); return Task.CompletedTask; }
    Task CapturePayment(string id) { Console.WriteLine($"pay {id}"); return Task.CompletedTask; }
    Task Confirm(string id) { Console.WriteLine($"confirm {id}"); return Task.CompletedTask; }
    Task ReleaseStock(string id) { Console.WriteLine($"release {id}"); return Task.CompletedTask; }
}

await new CheckoutSaga().RunAsync("o-1");

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• Steps are local; failure triggers compensation.
• Persist saga state in real systems.
• Deep dive compares choreography vs orchestration later.

Practice next

1. Run the happy path logs.
2. Throw in CapturePayment and watch release.
3. Make each step idempotent with keys.
4. Add email step after confirm.
5. Timeout cancel for stuck sagas.

Remember

Sequence + compensate. Local ACID only. Idempotent steps.

ShopNest checkout saga

Reserve → pay → confirm with release on failure.

Outcome: No silent reserved stock without payment.