Azure Service Bus Queue vs Topic EXPLAINED

#Azure Service Bus is a great tool to implement asynchronuous messaging in your systems. But what's the difference between Azure Service Bus Queue and Topic? You might be surprised, but a lot of people fail to unuderstand it. Not anymore! In this video I'll show you a simple and practical setup that showcases the difference between Azure Service Bus Queue and Topic. Bot only that. I also give some practical references on situations when you might want to use an Azure Service Bus queue and and you might want to use an Azure Service Bus topic.
Join this channel to get source code access and other perks:
/ @codewrinkles
Content
1. Intro: 00:00
2. Azure Service Bus setup
3. Sending messages: 01:44
4. Processing Queue messages: 04:32
5. Processing Topic messages: 06:10
6. Azure Service Bus Queue Vs Topic in practice: 07:47
7. Azure Service Bus Queue Vs Topic use cases: 09:29
Also follow me here (especially if you are a self taught developer):
✅My other channel: / @danpatrascutech
✅Facebook: / danpatrascutech
✅Instagram: / danpatrascutech
✅TikTok: / danpatrascutech

[@bogdanb904]

Given the scenario of 2 different consumers that are scaled out (X instances for each consumer), how would a topic subscription behave? Would all the instances receive the message? Or only one instance per each consumer type?

[@anonymoos]

Excellent explanation, thanks Dan! Follow up question though, how long does the processor have to mark the message as complete before another processor will pick up the same message? Is that built-in to the service bus, or is that something to implement on the processor side?

[@Codewrinkles]

Yep, when you create a topic or a queue you can define message lifetimes and other similar settings. If messages are then not picked up in that time frame, those messages are discarded.

[@afgone123456]

How about adding filter to topic subscription and send to only one subscription then have multiple consumers listening to that subscription only?

[@Codewrinkles]

That doesn't really jhelp as subscriptions behave similar to queues. One consumer will pick it up, but you don't know which one.