The Rule Pattern in C#, and Why It Works So Well with the Result Pattern Business rules rarely stay in one place. A small validation starts in a command handler. Another check appears in a service. A third gets added somewhere in the domain. A few...

Building a Clean Master-Detail App with Blazor Server, MudBlazor, and EF Core When building business applications, one of the most common requirements is a master-detail workflow. Orders and order items are a perfect example. You need a clean lis...

Building a Blazor Form with the Command Pattern and Undo In a typical Blazor form, inputs update the model directly. That is simple and works fine for basic CRUD screens, but it starts to feel limiting when you want more control over how changes hap...

Recently, I had a simple coding task. I needed to split an item's quantity across multiple lines. For example, I had Item 1 with a total quantity of 10, but that quantity could not remain on a single line. It had to be distributed across several lin...

If you ever had to “fix a batch” of invoices, reset workflow statuses, or reprocess failed documents, you know the pain, one mistake and you either update too much, or you update the right rows but lose the evidence of what changed. SQL Server has a...

When IDbContextFactory enters the chat, and what it actually fixes Most EF Core examples use a scoped DbContext. In a normal Web API request, that’s fine, the request ends, the context is disposed. Then you build Blazor Server. A Blazor Server ci...

ASP.NET Core already gives you solid logging out of the box, and if you want richer sinks and structured logs, Serilog is a common choice. But sometimes you cannot use a ready made sink, because the company already has a legacy logging table with a...

About 8 years ago I came across the Chain of Responsibility pattern. I remember I was genuinely happy when I understood it, because all those long if / else if / else blocks suddenly felt unnecessary. Instead of one method trying to decide everythin...

Carter in a CQRS API, advantages and alternatives. In this project I wanted the API layer to stay small and structured. I like minimal APIs, but I don’t like having 200 endpoints inside Program.cs. That’s why I used Carter, it keeps the minimal API...

The tech stack I used and why updated, with Repository and Unit of Work This project is small, but I wanted it to feel like a real API you can extend. The repository is here: https://github.com/stevsharp/ChainOfResponsibilityWithMediatR Carter f...

Chain of Responsibility inside CQRS with MediatR, a small practical example When we talk about “clean architecture” in ASP.NET Core, it is easy to end up with too many layers and too many rules, and the simple business logic becomes hard to read. T...

Why learning to build your own ORM is worth it even if you use EF Core or Dapper Most developers meet ORMs the same way they meet electricity, you flip a switch and things work. That’s great, until something gets slow, a query behaves oddly, or you...

1. Introduction Most .NET apps need some kind of background work. Sending emails, generating reports, cleaning data, all of these are better when they run automatically on a schedule, instead of being triggered by users. You do not always need a h...

Tutorial: Building a .NET 9 Console App with Hangfire and Channels Overview In this tutorial, you will build a .NET 8 console application that: Polls data from an API, or simulates it Uses System.Threading.Channels for producer consumer messagi...

Decorator pattern, in short The decorator pattern is a structural design pattern that lets you add behavior to an object at runtime by wrapping it with another object that has the same interface. The wrapper forwards calls to the inner object, then ...

The problem we’re solving Stuff goes wrong: timeouts, not-found resources, validation fails. You want one consistent error response and clean logs, without sprinkling try/catch everywhere. Two good options Option A — Global Exception Handler recom...

Introduction Distributed systems are powerful — but they come with one big challenge: reliability. What happens if your application updates a record in the database and then tries to publish a message to a message broker… but crashes in between? ...

MassTransit in ASP.NET Core: A Practical Guide to Event-Driven .NET Intro Event-driven architectures help teams decouple services, scale independently, and handle failures gracefully. MassTransit is a mature, open-source library that makes message-b...

Modern applications often need to broadcast events across multiple services. Think of an order being placed in an e-commerce system. The order service publishes an event, and multiple subscribers react independently: 1. the billing service charges ...

MassTransit has been around since 2007 and has matured into one of the most stable and feature-rich open-source .NET messaging frameworks. It acts like a factory for message brokers, meaning you can switch between providers such as RabbitMQ, Azure S...