Skip to main content

Automating MassTransit Consumer Registration

When working with MassTransit, registering consumers can become cumbersome if you have many of them. Luckily, MassTransit provides a way to register all your consumers automatically using AddConsumers. This post will guide you through the process of setting up and using AddConsumers to simplify your consumer registration.

What is MassTransit?

MassTransit is an open-source distributed application framework for .NET, which simplifies the creation and management of message-based systems. It supports various messaging platforms like RabbitMQ, Azure Service Bus, and Amazon SQS.



Setting Up MassTransit

Before diving into consumer registration, let’s quickly set up a MassTransit project.

Step 1: Install MassTransit Packages

First, install the necessary MassTransit packages via NuGet. You can use the following command on your favorite command line:

dotnet add package MassTransit.RabbitMQ

Step 2: Configure MassTransit

In your Program.cs or wherever you configure your services, set up MassTransit:

Registering Consumers Automatically

Manually registering each consumer can be tedious, especially in a large application. MassTransit provides the AddConsumers method, which scans and registers all consumers in your assembly.

Step 1: Create Your Consumers

First, let’s create a few consumers:

When registering consumers automatically, I recommend to add a consumer definition for each consumer. This allows us to specify the configuration applicable for every consumer:

Step 2: Register Consumers Automatically

Modify your MassTransit configuration to use AddConsumers:

AddConsumers will scan the specified assembly (in this case, the assembly containing the Program class) and registers all implementations of IConsumer it finds. It will also search for related ConsumerDefinition<T> implementations and load them as well.

By using this method MassTransit will automatically detect and configure the consumers, significantly reducing the boilerplate code required for consumer registration.

More information

Consumers · MassTransit

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...