Azure Service Bus Deep Dive (Azure & AI Conference 2022)
Вставка
- Опубліковано 18 кві 2022
- This session, the Azure Service Bus "Architect's Cut", is a deep dive that explains many of Service Bus's features and also goes into quite a bit of detail on the backend architecture of the service. This was recorde4d at the Azure & AI conference in Las Vegas in April 2022.
Slides at github.com/clemensv/messaging... - Авто та транспорт
Fantastic details. More, more, more.
Hi Clemens, Thanks for the wonderful presentation. I am looking to use Azure Service bus at organization level and wanted to know if there is some best practices that can be used for queue management and sharing Azure Service Bus across multiple application. I want to use Azure Service Bus as central place for sending notifications from application to application
Nice video!, How can I get the configuration data of an Azure Service Bus queue or topic automatically with powershell? thanks
if there is a downstream application of the consumer, is it possible for the downstream consumer to send the acknowledgement to the queue that the message was accepted and handled? Or it should be the consumer only which can send an acknowledgement ?
At 11:47 you say that the topic names are either flat or hierarchical but I can only see in service bus that they are Flat.... if i try and make a hierarchical name it just gets converted to warehouse~ab~siteA. Has this been removed as supported functionality? for my scenario i might have customerA/live/topic1 customerB/live/topic1 so being able to manage these hierarchically and apply a permission at the customerB/live point and have it cascade to all child topics would be great but i don't see how you do this.
How does the locking of messages work with multiple consumers (subscribers of topics) on the incoming message?
Each subscription has a distinct queue and locking there works like with any other queue. You can also have competing consumers on a subscription.
𝐩𝓻Ỗ𝓂Ø𝓈Ｍ ✌️