11 min read
Saga Pattern in .NET: Choreography vs Orchestration
Implement the Saga pattern in .NET for distributed transactions across microservices. Compare choreography vs orchestration with real C# examples.
Blog topic
Article index for CQRS-lite — when MediatR helps delivery, license vs Wolverine, and when a mediator is ceremony.
CQRS-lite on ASP.NET Core — start with MediatR and CQRS-lite, then the license vs Wolverine decision.
This page is the article map for CQRS-lite and MediatR decisions.
| You want… | Open |
|---|---|
| When MediatR helps delivery | MediatR and CQRS-lite |
| License vs Wolverine / stay / drop | MediatR license vs Wolverine |
CQRS means separate paths for reads and writes — not necessarily event sourcing. MediatR is one dispatcher, not a requirement.
Related: C# Design Patterns · Architecture
Ceremony vs delivery: MediatR and CQRS-lite. This page is the index.
No — commands and queries as separate requests can be plain services. See the CQRS-lite article for when MediatR earns its keep.
11 min read
Implement the Saga pattern in .NET for distributed transactions across microservices. Compare choreography vs orchestration with real C# examples.
6 min read
A practical ASP.NET Core decision guide after MediatR’s commercial licensing: when I stay on MediatR, when I migrate to Wolverine, and when CQRS does not need a mediator at all.
Updated Published 9 min read
MediatR in C# / ASP.NET Core — when CQRS-lite handlers and pipeline behaviors help a product team ship faster, and when extra folders slow healthcare and SaaS delivery down.