Subscribe! is a video blog about Messaging, Middleware, Architecture, and all sort of other interesting topics around building larger and more sophisticated solutions than your average website on Azure. The channel host is Clemens Vasters, Principal Architect at Microsoft.
Hello, hello. For the people here, asking how to connect the "MQTTX". Well, MQTTX or any other MQTT client will need to be configured basically in the same way: Broker URL, Port, and the most important The client certificate and the key. Once you do that, your client that could be anything will work perfectly. Personally, I like a lot MQTT Explorer so I always use that one. I entered the corresponding settings, I uploaded the Client Certficate and the key (this is Very important) and basically that's all. All works fine :)
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 ?
can you kindly explain how you setup MQTTX to connect to Azure Event Grid why don't you want to explain step by step how to configure everything, especially what everyone cares about the most mqttx also how to create a demo certificate for each mqtt client, you are avoiding the topic of how to configure everything and it irritates me a lot I know you are presenting possibilities, but for us engineers the most important thing is how everything works and how we can configure it to our needs so that our customer is satisfied. i f I show them that everything works, then I can find potential customers, if I show them how everything works on a real example I'm sorry for this tone, but it will definitely be financially beneficial for you to show step by step how to set up the mqqt client.
Thank you for your short and crisp tutorial for the Azure Event Grid. I have a question, how and what DB is preferred to save the published messages? I Have a scenario where I have 100 plus MQTT streams and I want to process and save the processed output into timeseries DB. And if needed users can pull up the historical data and see the trends etc. Thank you for your time and support.
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.
Azure Event Grid is a push style distribution of events. Azure Service Buss is a pull-style. Azure Event Hubs is a push-style or pull-style? The sever (Event Hubs) pushes the events to the consumer.? Or the consumer pull the events?
In Kafka we have brokers. We have the leader and the follower. If the leader server goes down, then the follower becomes the leader. Does Azure Event Hubs has something similar?
As I explain in this talk, an Event Hubs deployment, of which we have several hundred, is a 3-tier broker cluster consisting of usually more than 30 VMs spread across 3 availability zones (= independent data centers). If any component across these three tiers goes down, it is instantly replaced in its role by a predesignated secondary (follower). We can lose two entire data centers and your namespace will still be up.
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
এই চ্যানেল সাব্সক্রাইব করে নোটিফিকেশন অন করে দিন ru-vid.com/show-UCdMRJA7XyKM86DzXd6onKig আমার চ্যানেলের কনটেন্ট গুলো ভালো লাগলে লাইক, শেয়ার ও কমেন্ট করু
Hi, thanks for the videos. Session Flow Control is in the TLS layer, and Link Flow Control is above, in the application layer. Is this correct? And as i know, TCP itself has also Flow Control in its layer in the transport layer (layer4). Why is a Link Flow Control required? Is the Session Flow Control the same as the TCP Flow Control or is it again one above, additionally? Why do we have several Flow Controls on each layer/level? Why is a Link Flow Control needed if TCP already have a Flow Control? Appreciate any comments.
A lot of this flow control stuff seems like it would be handled for you via TCP, no? TCP with their sliding windows and what not. Is there and advantage to doing this up in the application layer too?
what is the difference between a channel and a link? It is too confusing. If channels are the same as links then why introduce two terms for the same thing?
channels are ephemeral and recreated upon every connection... Links are a higher abstraction and built on top of channels/sessions, which state can be persisted
hello, sir, By watching your videos i brought ethernet shield and arduino. What i am trying to do is access my ethernet shield or arduino from any remote location. But its not working , i tried port forwarding from my router. I can access them on my local network. So please help
