This is a made-up incident, but every piece of it is something I've seen in a real code review. A user's photo goes viral. Forty "liked your photo" pushes land on their phone in under a minute. Somewhere in the middle of that storm, a high-priority safety alert for the same user is generated. It arrives fourth from last.
Nothing crashed. No exception was logged. The notification service did exactly what it was written to do: loop over events, call the push vendor, move on.
So let's write the post-mortem the way a team would, blameless, with a timeline, root causes, and the fixes. The code below is the shape of the fix in .NET 10, with the heavy parts trimmed and marked.
Tech Skill Builder is $5/month for a very limited time only (normally $10). Grab it now before it goes back to $10. The complete, working, tested project behind this post ( facebook-notification-fanout-dotnet , Clean Architecture, 100+ tests, plus an in-depth PDF) is inside.…