Skip to content

Latest commit

 

History

History
145 lines (103 loc) · 8.23 KB

README.md

File metadata and controls

145 lines (103 loc) · 8.23 KB
Raw

ServiceStack.AzureServiceBus

Build status Nuget

This adds Azure Service Bus MQ Server option for the excellent ServiceStack framework.

As it relies on WindowsAzure.ServiceBus Nuget package, it requires .Net Framework 4.5 Full Profile.

This is inspired from the Rabbit MQ implementation and supports similar features (most of them are out-of-the-box ServiceStack features irrespective of the MQ Server option):

  • Messages with no responses are sent to .outq queue
  • Messages with responses are sent to the response .inq queue
  • Responses from messages with ReplyTo are published to that address
  • Messages with exceptions are re-tried then published to the respective dead-letter queue
  • OneWay HTTP requests are published to MQ then executed
  • OneWay MQ and HTTP Service Clients are Substitutable

ServiceStack has added MQ support for Azure Service Bus as part of their v4.5.14 release maintained at https://github.com/ServiceStack/ServiceStack.Azure.

I would recommend using the official implementation instead of this one if it covers your needs.

One reason you may want to give this non-official implementation a try is that you are not targeting .NET Core and you need some feature that is not part of the official MQ Server.

Ideally, the official package eventually offers all features (and likely more) and this repository can enjoy an early retirement.

Adding Azure Service Bus MQ support to ServiceStack

Create a Service Bus namespace in Azure and obtain the connection string from the Shared Access policies.

Install the package from Nuget.org

Install-Package ServiceStack.AzureServiceBus

Register Azure Service Bus MQ Server in your ServiceStack AppHost:

public override void Configure(Container container) 
{
    // ...

    // register the Azure MQ Server
    container.Register<IMessageService>(c => new AzureBusServer("Endpoint=sb://YOUR_SB_NAMESPACE.servicebus.windows.net/;SharedAccessKeyName=YOUR_ACCESS_KEY;SharedAccessKey=****"));

    var mqServer = container.Resolve<IMessageService>();

    mqServer.RegisterHandler<Hello>(ExecuteMessage);
    mqServer.Start();
}

Azure Service Bus MQ Features

The AzureBusServer has the configuration options:

  • int RetryCount - How many times a message should be retried before sending to the DLQ.
  • string connectionString - The connection string to the Azure Service Bus namespace
  • IMessageFactory MessageFactory - the MQ Message Factory used by this MQ Server
  • Func<IMessage, IMessage> RequestFilter - Execute global transformation or custom logic before a request is processed. Must be thread-safe.
  • Func<object, object> ResponseFilter - Execute global transformation or custom logic on the response. Must be thread-safe.
  • Action<QueueDescription> CreateQueueFilter - A filter to customize the options Azure Queues are created/updated with.
  • Action<string, BrokeredMessage> GetMessageFilter - Called every time a message is received.
  • Action<string, BrokeredMessage, IMessage> PublishMessageFilter - Called every time a message gets published.
  • string[] PriorityQueuesWhitelist - If you only want to enable priority queue handlers (and threads) for specific message types. All message types have priority queues by default.
  • bool DisablePriorityQueues - No priority queue will be created or listened to.
  • string[] PublishResponsesWhitelist - Opt-in to only publish responses on this whitelist. All responses are published by default.
  • bool DisablePublishingResponses - No response will be published.

As an alternative to a connection string, you can pass an instance of AzureBusMessageFactory to the AzureBusServer constructor and provide your own NamespaceManager and MessagingFactory.

Starting the MQ Server will create up to 2 threads for each handler, one to listen to the Message Inbox {RequestDto}.inq and another to listen on the Priority Queue located at {RequestDto}.priorityq.

Queue names are limited to alphanumeric, period, hyphen and underscore in Azure Service Bus. As such, the default prefixes from QueueNames and the queue name resolver get overriden by AzureBusMessageFactory. The deadletter queue name resolves to RequestDto.inq/$deadletterqueue. Finally, note that queue names are case-insensitive in Azure Service Bus.

By default, only 1 thread is allocated to handle each message type, but like the other MQ Servers is easily configurable at registration:

mqServer.RegisterHandler<Hello>(m => { .. }, noOfThreads:4);

Behind the scenes, it delegates the work to Azure Service Bus event-driven message pump.

Create Queue Filter

To modify the options a queue gets created with, provide a CreateQueueFilter filter and modify the QueueDescription.

For instance, to change the default TTL and have messages expire automatically after 2 minutes:

 container.Register<IMessageService>(c => new AzureBusServer(ConnectionString) {
     CreateQueueFilter = (description) => {
                    description.DefaultMessageTimeToLive = TimeSpan.FromMinutes(2);
                }
 });

If the queue already exists, any change to the queue options will result in an update.

Message Filters

There are optional PublishMessageFilter and GetMessageFilter callbacks which can be used to intercept outgoing and incoming messages. The Type name of the message body that was published is available in the Label property, e.g:

mqServer.PublishMessageFilter = (queueName, brokeredMsg, message) => {
    brokeredMsg.Properties["AppId"] = "app:{0}".Fmt(queueName);
};

mqServer.GetMessageFilter = (queueName, brokeredMsg) => {
    receivedMsgType = brokeredMsg.Label; //automatically added by AzureBusMessageProducer
    receivedMsgApp = brokeredMsg.Properties["AppId"] as string;

    receivedMsgType.Print(); // Hello
    receivedMsgApp.Print(); // app:Hello.In
};

using (var mqClient = mqServer.CreateMessageQueueClient())
{
    mqClient.Publish(new Hello { Name = "Bright blue sky" });
}

Note that the brokeredMsg parameter of GetMessageFilter can be null when explicitly retrieving a message results in a timeout.

Whitelisting priority messages and publishing responses

By default, all registered handlers will result in listening to a normal priority queue and a high priority queue. As well, all message responses get published to their respective queues.

Priority messages and publishing responses can be entirely disabled by setting DisablePriorityQueues and DisablePublishingResponses respectively to true.

It is also possible to whitelist the priority queues and responses to publish by message type.

// only use a priority queue for Hello messages 
mqServer.PriorityQueuesWhitelist = new[] { nameof(Hello) };

// only publish HelloResponse responses
mqServer.PublishResponsesWhitelist = new[] { nameof(HelloResponse) };

Upcoming Features

  • error handler