Flaminco.AzureBus.AMQP 2.0.6

Flaminco.AzureBus.AMQP

Flaminco.AzureBus.AMQP is a .NET library that simplifies the integration of AzureBus AMQP 1.0 in your applications. This library provides a clean and easy-to-use API for creating consumers and publishers to interact with AzureBus queues.

Installation

You can install the package via NuGet Package Manager:

dotnet add package Flaminco.AzureBus.AMQP

Or via the Package Manager Console in Visual Studio:

Install-Package Flaminco.AzureBus.AMQP

Getting Started

Step 1: Configure the AMQP Client

First, you need to configure the AMQP client in your application's Startup or Program class:

builder.Services.AddAMQPClient<Program>(options =>
{
    options.ConnectionString = "<Azure Bus Connection String>";
});

Step 2: Create a Message Publisher

Implement a custom publisher by extending the MessagePublisher class. The publisher defines the queue(s) to which it will send messages:

    public class PersonPublisher : MessagePublisher
    {
        public PersonPublisher(IOptions<AMQPClientSettings> clientSettings) : base(clientSettings)
        {
        }

        protected override string Name => nameof(PersonPublisher);
        protected override string[] Queues => ["HelloQueue"];
    }

Step 3: Send a Message

Now, you can use your custom publisher to send a message to the specified queue:

  public class Example(IAMQPLocator _amqpLocator)
    {
        [HttpGet]
        public async Task PushMessage(CancellationToken cancellationToken)
        {
            await using MessagePublisher helloPublisher = _amqpLocator.GetPublisher<PersonPublisher>();

            await helloPublisher.PublishAsync(new Person
            {
                Name = "Ahmed Abuelnour",
                Age = 30
            }, cancellationToken);
        }
    }

Step 4: Create a Message Consumer

Implement a custom consumer by extending the MessageConsumer class. The consumer defines the queue from which it will receive messages:

    public class PersonConsumer : MessageConsumer
    {
        public PersonConsumer(IOptions<AMQPClientSettings> clientSettings, IPublisher publisher) : base(clientSettings, publisher)
        {
        }

        protected override string Name => nameof(PersonConsumer);
        protected override string Queue => "HelloQueue";
    }

Step 5: Implement a message handler

IMessageFaultHandler is Optional to handle the cases where the consumer couldn't deal with the incoming message, and of course you can have multiple handlers for the same message.

    public class PersonMessageHandler : IMessageReceivedHandler<Person>, IMessageFaultHandler<Person>
    {
        public async Task Handle(MessageReceivedEvent<Person> notification, CancellationToken cancellationToken)
        {
            Console.WriteLine($"I got a new message saying: {notification.Message}");
        }

        public async Task Handle(MessageFaultEvent<Person> notification, CancellationToken cancellationToken)
        {
            Console.WriteLine($"fault message from: {notification.Name}, and queue: {notification.Queue}");
        }
    }

Step 6: Register the consumers to be marked as background service

Finally, register your consumers in the dependency injection container in your Startup or Program class:

    builder.Services.AddAMQPService<PersonConsumer,Person>();

Step 7: Important Notes

• Queue Creation: Azure Service Bus does not automatically create queues or topics. You must manually create them in the Azure portal or using the Azure Management API.

• Queue/Topic Lookup: When the application starts, it will attempt to verify that the queue name specified for the consumer exists. If the queue is not found, the system will search for a topic with the same name as the queue. Additionally, it will look for a subscription matching the consumer's name.

• Error Handling: It's important to implement fault handling for scenarios where the consumer encounters errors while processing messages. You can achieve this using the optional IMessageFaultHandler.

Step 8: Run the Application

Build and run your application. The consumer will continuously listen for messages on the specified queue, while the publisher sends messages to that queue.

Contributing

If you encounter any issues or have suggestions for improvements, please feel free to contribute by submitting an issue or a pull request.

License

This project is licensed under the MIT License.