Why should you care?

ShopNest placing an order may write Order + Outbox rows that must commit together.

See it live — copy this example

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

public interface IUnitOfWork { Task CommitAsync(); }
public sealed class OrderUnitOfWork : IUnitOfWork
{
    private readonly List<Func<Task>> _work = new();
    public void Register(Func<Task> action) => _work.Add(action);
    public async Task CommitAsync()
    {
        foreach (var a in _work) await a();
        Console.WriteLine("committed");
    }
}

var uow = new OrderUnitOfWork();
uow.Register(() => { Console.WriteLine("insert order"); return Task.CompletedTask; });
uow.Register(() => { Console.WriteLine("insert outbox"); return Task.CompletedTask; });
await uow.CommitAsync();

Run Example »

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

What happened?

• Registered actions run then commit.
• With EF, UoW usually calls SaveChangesAsync once.
• Do not hold DB transactions open across HTTP calls to payment providers.

Practice next

1. Commit the sample work list.
2. Map to DbContext.SaveChangesAsync in real code.
3. Include outbox insert in the same commit.
4. Simulate failure before commit.
5. Return number of operations committed.

Remember

One business commit. Track related changes. Keep external I/O outside.

ShopNest order+outbox UoW

Place-order commits both rows atomically.

Outcome: No order without its event row.