Distributed Messaging Made Easy With Wolverine & RabbitMQ

Want to master Clean Architecture? Go here: https://bit.ly/3PupkOJ
Want to unlock Modular Monoliths? Go here: https://bit.ly/3SXlzSt

Wolverine docs: https://wolverinefx.net/introduction/what-is-wolverine.html

In this video, I’ll show you how to connect RabbitMQ with the Wolverine messaging library and use them together in a .NET application to build real distributed messaging.

We’ll start with a baseline Wolverine setup (local queues), then move the same command/event flow to RabbitMQ using .NET Aspire so you can run the broker locally and wire everything up with minimal friction.

However, connecting the broker is only half the battle. I also ran into a specific "gotcha" where Wolverine was still routing messages locally despite the RabbitMQ configuration. I’ll show you exactly how to fix this using DisableConventionalLocalRouting so your messages actually go through the broker.

What you’ll learn
- Baseline Wolverine messaging (command + event handlers)
- Running RabbitMQ with .NET Aspire (including the management UI)
- Configuring Wolverine’s RabbitMQ transport (Aspire-friendly setup)
- Auto-provisioning exchanges/queues + conventional routing
- The common “gotcha”: why Wolverine can still process messages locally in a single process, and the one line that forces RabbitMQ transport
- Verifying publish/consume using OpenTelemetry tracing

Check out my courses:
https://www.milanjovanovic.tech/courses

Read my Blog here:
https://www.milanjovanovic.tech/blog

Join my weekly .NET newsletter:
https://www.milanjovanovic.tech

Chapters

Видео Distributed Messaging Made Easy With Wolverine & RabbitMQ канала Milan Jovanović