Used for event-driven architecture. Similar to Service Bus you need to set up RabbitMQ Windows Service
It works on AMQP Protocol
It provides APIs and.Net Packages to communicate to RabbitMQ. Use RabbitMQ Client Package, Create ConnectionFactory. It uses Hostname where this service is installed, Username, and Password. Need to explore more what are the other authentication mechanism. This will be used to create queues, topics, and send messages. You can create a dynamic queue that is valid for scope.
It also have Admin UI portal to monitor all the queue.
Admin UI
It provides multiple options to create Queue, Create Exchange. The exchange type could be Topics, Fanout, etc.
Do the binding of the queue to the exchange type
Option for send test message, Purge-it or read the messages
Message Persistent and durable queue
It depends on how you create the queue. If it durable queue then the queue will persist irrespective of server restart this will be no loss of message.
Message Exchange Pattern
One to one: The sender sends and the receiver receives.
WorkerQueue: Sender sends and multiple receivers but one of them will receive
Topic Subscribe(Fanout pattern): Send sender and all receivers will receive
Remote Procedure Call Pattern: It is a request and response pattern same as Service Bus