RabbitMQ in .NET Core (Part 1, Single producer and consumer with Queue)

This is the first video of the video series on RabbitMQ. RabbitMQ is vast, and it is not possible to cover every single aspect of RabbitMQ in a single video. Hence, I will create a series of RabbitMQ.

Before we get into RabbitMQ it is important to understand why we need a queueing system. And I discussed this in my video on Microservices here:

Microservices introduction:    • What are Microservices in ASP.NET Cor...  
Hands-on microservices:    • Converting a Monolithic Application i...  

A queue or a message broker provides the much-needed decoupling between microservices. And it prevents get into the anti-pattern of the distributed monolith.

You can think of a message broker like a post office. Its main responsibility is to broker messages between publishers and subscribers.

Once a message is received by a message broker from a producer, it routes the message to a subscriber. The message broker pattern is one of the most useful patterns when it comes to decoupling microservices.

The source code for this video is available in my GitHub repo here: https://github.com/choudhurynirjhar/r...