Great video! Thank you!!! The reason I had to search on UA-cam was that I cannot get MT to work on Azure - IMHO the official documentation is missing the point: MT does not work on Basic Tier.
This code currently hangs on publish and doesn't return. I updated the calling code to use async and await as well. Configuration is pretty simple as well.
If it's hanging, you can't reach Azure Service Bus from your machine. If you pass a cancellationToken to Publish, you can cancel it (after a timeout, for instance). The logs will reveal the why.
So if i have two solutions, one i'm using to listen with masstransit, and one where i'm using the azure service bus setup without masstransit to publish messages. Would that be possible?
@@PhatBoyG Well not that much of a context in the video tbh, - Consumer configuration using Azure Service Bus - Starting the producer (which is the worker in your case) - Finally Checking the overview in Azure and there Mr Chris you can see a Queue and a Topic created lol. So my question again is why do we have them both ?
@@yasserkharab9722 if you have consumers that consume message types, topics and subscriptions are created. The final topology is documented: masstransit-project.com/advanced/topology/servicebus.html#broker-topology
Excellent video. The semantics of MT have thrown me a few times and your practical descriptions were straightforward. Thank you!
Wow, using interfaces are already "old" 3:19... A white hair just popped up
I love to see how MT has evolved. Great stuff!
Great video! Thank you!!! The reason I had to search on UA-cam was that I cannot get MT to work on Azure - IMHO the official documentation is missing the point: MT does not work on Basic Tier.
Right at the top highlighted: masstransit.io/documentation/configuration/transports/azure-service-bus
This code currently hangs on publish and doesn't return. I updated the calling code to use async and await as well. Configuration is pretty simple as well.
If it's hanging, you can't reach Azure Service Bus from your machine. If you pass a cancellationToken to Publish, you can cancel it (after a timeout, for instance). The logs will reveal the why.
Why are you adding consumer before publisher? I think it would make more sense vice-versa.
Maybe i missed it, but why does the basic tier not really work with MassTransit? Is this only because the basic tier does not include Topics?
Basically.
Is it possible to add only the consumers in mass transit, and still consume from actual azure service bus that isnt configured with mass transit?
I don't understand what you mean, adding consumers to MassTransit is meant for consuming messages using... MassTransit.
So if i have two solutions, one i'm using to listen with masstransit, and one where i'm using the azure service bus setup without masstransit to publish messages. Would that be possible?
@@TheJybbe sure, you can configure MassTransit to consume raw JSON messages if that's what the other application is producing.
Topic and queue at the same time ?
It may help to rephrase your question in the form of an actual question, with some context.
@@PhatBoyG Well not that much of a context in the video tbh,
- Consumer configuration using Azure Service Bus
- Starting the producer (which is the worker in your case)
- Finally Checking the overview in Azure and there Mr Chris you can see a Queue and a Topic created lol.
So my question again is why do we have them both ?
@@yasserkharab9722 if you have consumers that consume message types, topics and subscriptions are created. The final topology is documented: masstransit-project.com/advanced/topology/servicebus.html#broker-topology