A use case isn’t a transaction. The moment it touches more than one system, you are dealing with partial failure. Here’s how I classify side effects and design use cases that fail loudly and recover safely.
When Your Use Case Half-Succeeds: Designing for Partial Failure in .NET
calendar_today
May 16, 2026
person
milan@milanjovanovic.tech (Milan Jovanović)
domain
modular-monolith