I created solution for mass document processing where single document processing time is about 10-30s long.
When It will be processed using one queue, when one client post 100 docs to queue, second client with one doc will be wait for result too long.
So I modified topology to direct exchanges with client ID as routingKey, and it works fine.
But, when I need to enable another client ID I must restart service.
So I looking for solution to do:

I created solution for mass document processing where single document processing time is about 10-30s long.
When It will be processed using one queue, when one client post 100 docs to queue, second client with one doc will be wait for result too long.
So I modified topology to direct exchanges with client ID as routingKey, and it works fine.
But, when I need to enable another client ID I must restart service.
So I looking for solution to do:

I created solution for mass document processing where single document processing time is about 10-30s long.
When It will be processed using one queue, when one client post 100 docs to queue, second client with one doc will be wait for result too long.
So I modified topology to direct exchanges with client ID as routingKey, and it works fine.
But, when I need to enable another client ID I must restart service.
So I looking for solution to do:

I have a simple code as bellow, I can see that the memory keeps increase forever. I’m not sure what I am missing here.

I have a simple code as bellow, I can see that the memory keeps increase forever. I’m not sure what I am missing here.

I have a simple code as bellow, I can see that the memory keeps increase forever. I’m not sure what I am missing here.

Trying to use consume/publish filters for logging purposes and everything was going smooth until I came across a microservice that uses batch consumers, where it will throw a nullreferenceexception if a batch consumer is registered.
Here’s how our MassTransit is configured:

Trying to use consume/publish filters for logging purposes and everything was going smooth until I came across a microservice that uses batch consumers, where it will throw a nullreferenceexception if a batch consumer is registered.
Here’s how our MassTransit is configured:

I was reading the following documentation link regarding the Claim Pattern in MassTransit and I was wondering if I’ve to run that command

I have an existing email service implementation that listens on an Azure Service Bus and uses the native library Azure.Messaging.ServiceBus.
I need now to add a separate processing for other kind of email and I would like to handle the message with MassTransit as I’ve done for other portion of the infrastructure we have.