Hey Chris! I know it's been several months since you put this video up. We have a decently sized enterprise solution using MassTransit by way of Azure Functions/Azure Service Bus. We're now in the process of working on another, but now we can use Azure Functions v3. So I'll be sure to give you some feedback when we dig into this. Based on what I'm seeing in this video, it already looks way nicer to configure though!
Dunno if you get a notification for this but: we're currently testing out our new Function App using MassTransit. So far, working with Azure Functions v3 with DI is way nicer than our "make everything static Lazy" in v2. MassTransit is great as always - we decided to go with it over using just pure ASB/AF mainly because of how easy the Consumers are to build and unit test (even though it was very close - pure ASB/AF is surprisingly great.) We're also digging that the for MassTransit for Azure Functions registration includes everything we need, so our timer function that needs an IPublishEndpoint injected is able to get one without additional configuration. We were already familiar with building a bootstrapping console application to spin up the infrastructure, so no issues there. The experience has been a rather positive one. Overall, I'd say you did a phenomenal job with the Azure Function/MassTransit integration.
Is is somehow possible to use a "general" function that receives all types of messages that are sent to a specific queue/subscription and sends them to the specific consumers? Or should I create a specific function for each type of message?
MassTransit will dispatch the message to any configured consumers for that function. Since the message type is in the envelope, only those consumers interested in the message will consume it. MassTransit is already handling all of the type-based dispatch for you. that said, it's smart to separate your various message types into queues based upon business requirements to avoid bottlenecks with every message going through a single queue.
When using MassTransit, you don't need output bindings. MassTransit will send/publish messages to Azure Service Bus itself, without using the binder/collector types.
Hey Chris! I know it's been several months since you put this video up. We have a decently sized enterprise solution using MassTransit by way of Azure Functions/Azure Service Bus. We're now in the process of working on another, but now we can use Azure Functions v3. So I'll be sure to give you some feedback when we dig into this. Based on what I'm seeing in this video, it already looks way nicer to configure though!
Dunno if you get a notification for this but: we're currently testing out our new Function App using MassTransit. So far, working with Azure Functions v3 with DI is way nicer than our "make everything static Lazy" in v2. MassTransit is great as always - we decided to go with it over using just pure ASB/AF mainly because of how easy the Consumers are to build and unit test (even though it was very close - pure ASB/AF is surprisingly great.) We're also digging that the for MassTransit for Azure Functions registration includes everything we need, so our timer function that needs an IPublishEndpoint injected is able to get one without additional configuration. We were already familiar with building a bootstrapping console application to spin up the infrastructure, so no issues there. The experience has been a rather positive one. Overall, I'd say you did a phenomenal job with the Azure Function/MassTransit integration.
@@vordrax1014 thanks, glad it is working well for you!
Hey, very nice. I’m trying to improve the communication between Api services, and I will use azure service bus, does I need use azure functions too?
Is is somehow possible to use a "general" function that receives all types of messages that are sent to a specific queue/subscription and sends them to the specific consumers?
Or should I create a specific function for each type of message?
MassTransit will dispatch the message to any configured consumers for that function. Since the message type is in the envelope, only those consumers interested in the message will consume it. MassTransit is already handling all of the type-based dispatch for you. that said, it's smart to separate your various message types into queues based upon business requirements to avoid bottlenecks with every message going through a single queue.
Where did the repo go?
github.com/MassTransit/MassTransit/tree/v6.3.2/src/Samples/Sample.AzureFunctions.ServiceBus
How about output bindings?
When using MassTransit, you don't need output bindings. MassTransit will send/publish messages to Azure Service Bus itself, without using the binder/collector types.