Masstransit request response how to#

The term 'sender' is used for a Service Bus queue client or a topic client that sends messages to a Service Bus queue or a topic. A client can take the role of a sender or a receiver. Throughout this article, the term 'client' refers to any entity that accesses Service Bus. The second part provides guidance on using Service Bus in a way that can offer the best performance in a given scenario. The first part of this article describes different mechanisms to increase performance.

Masstransit request response how to#

RabbitMQ, AzureSB) you choose.Įnjoy! Posted on AugAuthor maldworth Categories design, programming Tags ASP.This article describes how to use Azure Service Bus to optimize performance when exchanging brokered messages. There you have it, pretty simple, but powerful features provided by MassTransit ontop of whatever message transport (eg. You can actually look and see what the RequestId is with context.RequestId.

It makes sure that it responds and retains the RequestId. This is the other part of the MassTransit value add plumbing. Open up CheckOrderStatusConsumer.cs and you will see: public async Task Consume(ConsumeContext context)Ĭ('Received OrderId: ' + ) Ĭontext.Respond(new SimpleOrderStatusResult ) Īnd the important line here is context.Respond(…). Now we take a quick peek in the Consumer. Then you would get the exact same behavior. Return bus.CreateRequestClient(address, requestTimeout) So in our RequestClientModule.cs, you could replace the builder.Register with: builder.Register(c => Return new MessageRequestClient(bus, address, timeout, ttl, callback) TimeSpan? ttl = default(TimeSpan?), Action> callback = null) If we look at the MassTransit source, we will see the extension is just that, a helper: public static IRequestClient CreateRequestClient(this IBus bus, Uri address, TimeSpan timeout, You might be wondering why I used MessageRequestClient? Because in the official sample, a helper extension method is used instead. It handles the plumbing of creating a RequestId and correlates messages accordingly. Line 4: This is where our concrete type MessageRequestClient is constructed, which is one of the many value adds for MassTransit. TimeSpan requestTimeout = TimeSpan.FromSeconds(30) īuilder.Register(c => new MessageRequestClient(c.Resolve(), address, requestTimeout)) You will see: Uri address = new Uri(ConfigurationManager.AppSettings) But for Request Response, we will use IRequestClient. When using Publish + Subscribe, we typically get the IBus or IBusControl injected and use the. So I will reduce the scope of this tutorial to registering the IRequestClient in an Ioc Framework (Autofac). Now there is excellent documentation here. *Update*: When I had drafted this, the MassTransit Documentation didn’t have an example for Request/Response. You can follow along with the completed project here. This tutorial will simply show the main components required to set up a Request/Response with MassTransit. If you have followed some of my other tutorials, you will know that I like to separate the RabbitMQ config with a virtual host and username specific to the tutorial. So this tutorial will show how this can be achieved with MassTransit. However, the need may arise to use request + response in a distributed system.

This is because distributed systems operate in different processes on different machines, giving it the benefit of horizontal scaling (with trade offs, but that’s another discussion entirely). Messages send with MassTransit typically are fire and forget.