System Design
How We Deliver 15 Million Webhooks a Day Without Losing a Single Event
Delivering 15M webhooks a day to endpoints you don't control is deceptively hard. Here's the outbox + queue + retry design that never drops an event.
20 min read10
Scalability, caching, queues, and trade-offs.
6 posts · 8 questions
Delivering 15M webhooks a day to endpoints you don't control is deceptively hard. Here's the outbox + queue + retry design that never drops an event.
How Mattrx swapped synchronous REST calls for Kafka — decoupling the ingestion pipeline, killing cascading failures, and cutting failures by 90%.
Clean Architecture in .NET — the Dependency Rule, four layers, full ASP.NET Core + EF Core + MediatR code, trade-offs, and the version that ships.
CQRS in .NET — the problem it solves, MediatR + EF Core implementation, separate read/write models, and when CQRS pays off vs over-engineering.
Azure Functions in .NET — when to pick them over Web API, hosting plans, HTTP/Queue/Timer/Durable code, cold starts, and the real cost model.
Outbox pattern in .NET — the dual-write problem, EF Core implementation, relay/dispatcher code, CDC vs polling, and the pitfalls that break production.