14 Years of Enterprise ASP.NET, Part 3: Performance, Microservices & Design Patterns That Earn Their Keep
Part 3 of a 14-year ASP.NET series: the performance techniques that move p95, when microservices help, and the patterns that earn their keep.
Scalability, caching, queues, and trade-offs.
6 posts · 8 questions
Part 3 of a 14-year ASP.NET series: the performance techniques that move p95, when microservices help, and the patterns that earn their keep.
Mattrx runs Azure Service Bus, Event Grid, and Kafka side by side. The decision framework, real code, and exactly when to pick each.
Our dashboards aggregated a 1.2-billion-row table at 2,100ms. Here's the partitioning, columnstore, and read-model design that got us to 48ms, with code.
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.