Dkeshri.MessageQueue.RabbitMq 2.0.6

About

This will help the user manage the connection and allow them to send messages to the RabbitMQ queue. Additionally, there is a RabbitMQ queue receiver that retrieves the messages.

Package Dependency

Dkeshri.MessageQueue

How to Configure

This package uses the IServiceCollection to setup. We have an Extension Method AddMessageBroker in Dkeshri.MessageQueue provide MessageBroker object to setup Message Broker Propery.

There is another extension method AddRabbitMqServices provided in Dkeshri.MessageQueue.RabbitMq is use to setup RabbitMq Connections.

AddRabbitMqServices is extention to MessageBroker

Register Sender

Note Make sure to set RegisterSenderServices to true

Sender For Exchange When you want to send message to Exchange this is the prefered way.

Step 1

services.AddMessageBroker(messageBroker =>
{
    messageBroker.RegisterSenderServices = true; // Set True to register Sender services
    messageBroker.ClientProvidedName = "Sender"; // Sender or Any name you like
    messageBroker.MessageBroker.ExchangeRoutingKey = "RoutingKey";
    messageBroker.AddRabbitMqServices((rabbitMqConfig) =>
    {
        rabbitMqConfig.HostName = "RabbitMqHost";
        rabbitMqConfig.Port = 5672; // your RabbitMq Port
        rabbitMqConfig.UserName = "username";
        rabbitMqConfig.Password = "password";
        rabbitMqConfig.Exchange.ExchangeName = "Your_ExchangeName";
    });
});

Step 2

There is an IStartup Interface provided by Message Broker, that will use Init Exchange, Please call it in main method, this interface is Registed in IServiceCollection DI container.

internal class MessageBrokerInitService : IMessageBrokerInitService
{
    IStartup _startup;
    public MessageBrokerInitService(IStartup startup)
    {
        _startup = startup;
    }

    public void InitMessageBroker()
    {
        _startup.OnStart();
    }
}

Sender For Queue When you want to send message to queue not to Exchange

services.AddMessageBroker(messageBroker =>
{
    messageBroker.RegisterSenderServices = true; // Set True to register Sender services
    messageBroker.ClientProvidedName = "Sender"; // Sender or Any name you like
    messageBroker.MessageBroker.ExchangeRoutingKey = "RoutingKey";
    messageBroker.AddRabbitMqServices((rabbitMqConfig) =>
    {
        rabbitMqConfig.HostName = "RabbitMqHost";
        rabbitMqConfig.Port = 5672; // your RabbitMq Port
        rabbitMqConfig.UserName = "username";
        rabbitMqConfig.Password = "password";
        rabbitMqConfig.Queue.QueueName = "YourQueueName";
    });
});

Register Receiver

Note Make sure to set RegisterReceiverServices to true. If you only want to reveive message from Queue then Please do not provide ExchangeName and RoutingKeys.

services.AddMessageBroker(messageBroker =>
{
    messageBroker.RegisterReceiverServices = true; // Set to True to register Receiver services.
    messageBroker.ClientProvidedName = "Receiver"; // Receiver or Any name you like
    messageBroker.AddRabbitMqServices((rabbitMqConfig) =>
    {
        rabbitMqConfig.HostName = "RabbitMqHost";
        rabbitMqConfig.Port = 5672; // your RabbitMq Port
        rabbitMqConfig.UserName = "username";
        rabbitMqConfig.Password = "password";
        rabbitMqConfig.Queue.QueueName = "YourQueueName";
        rabbitMqConfig.Queue.ExchangeName = "YourSenderExchangeName";
        rabbitMqConfig.Queue.RoutingKeys = [ "routingKey1" ];
    });
});

Note: Idealy One Application is Sender and other application is receiver. but you can configure both sender/receiver in one application too.

How to Use

In Sender Application

The IMessageSender interface is provided for the sender, offering the following methods:

• SendToQueue(string message)
• SendToQueue(string queueName, string message)
• SendToExchange(string message, string? routingKey);

You can specify the queueName when sending messages to RabbitMQ.

The IMessageSender interface is registered during the configuration phase in the IServiceCollection dependency injection container and can be injected into your class constructor, as demonstrated in the code below:

class SendMessageToRabbitMq : ISendMessageToRabbitMq
{
    private IMessageSender SendMessage { get; }
    public SendMessageToRabbiMq(IMessageSender sendMessage)
    {
        SendMessage = sendMessage;
    }

    public bool SendMessageToRabbitMq(string DataToSend)
    {
        return SendMessage.SendToQueue(DataToSend);
    }

    public bool SendMessageToRabbitMq(string queueName, string DataToSend)
    {
        return SendMessage.SendToQueue(queueName,DataToSend);
    }
    public bool SendMessageToRabbitMqExchange(string queueName, string DataToSend)
    {
        return SendMessage.SendToExchange(DataToSend,"routingKey1");
    }

}

Register SendMessageToRabbiMq in IServiceCollection

var builder = Host.CreateDefaultBuilder(args);
builder.ConfigureServices((hostContext, services) =>
{
    services.AddMessageBroker(messageBroker =>
    {
        messageBroker.RegisterSenderServices = true; // Set True to register Sender services
        messageBroker.ClientProvidedName = "SenderTest"; // Sender or Any name you like
        messageBroker.MessageBroker.ExchangeRoutingKey = "RoutingKey";
        messageBroker.AddRabbitMqServices((rabbitMqConfig) =>
        {
            rabbitMqConfig.HostName = "RabbitMqHost";
            rabbitMqConfig.Port = 5672; // your RabbitMq Port
            rabbitMqConfig.Exchange.ExchangeName = "Your_ExchangeName";
            rabbitMqConfig.UserName = "username";
            rabbitMqConfig.Password = "password";
        });
    });

    // register Sender Service in Services
    services.AddSingleton<ISendMessageToRabbitMq, SendMessageToRabbiMq>();

});


var host = builder.UseConsoleLifetime().Build();

using (var scope = host.Services.CreateScope())
{
    var startUp = scope.ServiceProvider.GetRequiredService<IStartup>();
    startUp.OnStart();
}

host.RunAsync().Wait();

In Receiver Application

The IMessageReceiver interface includes a delegate: Predicate<string>? MessageHandler.

This allows you to provide a callback method that will be invoked when a message is received from the RabbitMQ queue.

Note: Ensure that RegisterReceiverServices is set to true during configuration. This is necessary for the IMessageReceiver interface to be provided.

As demonstrated in the code below:

var builder = Host.CreateDefaultBuilder(args);
builder.ConfigureServices((hostContext, services) =>
{
    services.AddMessageBroker(messageBroker =>
    {
        messageBroker.RegisterReceiverServices = true; // Set to True to register Receiver services.
        messageBroker.ClientProvidedName = "Receiver"; // Receiver or Any name you like
        messageBroker.AddRabbitMqServices((rabbitMqConfig) =>
        {
            rabbitMqConfig.HostName = "RabbitMqHost";
            rabbitMqConfig.Port = 5672; // your RabbitMq Port
            rabbitMqConfig.UserName = "username";
            rabbitMqConfig.Password = "password";
            rabbitMqConfig.Queue.QueueName = "YourQueueName";
            rabbitMqConfig.Queue.ExchangeName = "Your_ExchangeName";
            rabbitMqConfig.Queue.RoutingKeys = [ "routingKey1" ];
        });
    });
});

var host = builder.UseConsoleLifetime().Build();

using (var scope = host.Services.CreateScope())
{
    var messageReceiver = scope.ServiceProvider.GetRequiredService<IMessageReceiver>();
    messageReceiver.MessageHandler = (message) =>
    {
        // After Process Message and return boolean value.
        Console.WriteLine(message);

        // message will only acknowledge to RabbitMq Service if return true.
        return true; 
    };
}
host.RunAsync().Wait();

Rabbit MQ SetUp

Generally in Message Queue system Producer(Sender) and Consumer(Reciver) are saperate application therefore best practice to implement RabbitMq Configuration is to have one Connection per Process Or Application and one Channel per thread.

We follow this convention to have one connection per process and one channel per thread.

So in our current implimentation sender and reciver are on same application so we share one connection to both sender and reciver of message queue. and also we have one channel through of application.

but we can also create two channel one for sender and one for reciver.

Note: If our sender and receiver have two application then we also create two connection. and each connection have there respective channels depending upon there need.

Docker Container Creation

Run below command to create RabbitMq Docker container

docker run -d -v rabbitmqv:/var/log/rabbitmq --hostname rmq --name RabbitMqServer \
-p 5672:5672 -p 8080:15672 rabbitmq:3.13-management

Port Detail

Port 8080 is for management portal and access by below mention Login credentials.

Click on the link for <a href='http://localhost:8080/'>Admin Portal</a>

Port 5672 is use in communication during producing and consuming of message.

Login crediential

Default login crediential if we not specifiy during creation of docker container

<small style='color:green'>Username</small> guest and <small style='color:green'>Password</small> guest