Azure Queue Storage Tutorial
ฝัง
- เผยแพร่เมื่อ 12 มิ.ย. 2024
- Azure Queue Storage is simple yet powerful service for storing large number of messages. It is one of core services for implementing scenarios like load-leveling, fan-out, fan-in and those relying on retry capabilities.
In this episode I give you introduction to what Storage Queue service is. How can you provision it, what are the typical scenarios that you would want to leverage its capabilities?
In this episodes live demo of
- Creating queue storage
- Managing queues and their data
- Implementing fan-out scenario using Logic Apps and Queues
Next steps for you after watching the video
1. What is azure queue service
- docs.microsoft.com/en-us/azur...
2. Managing queue data from Azure Portal
- docs.microsoft.com/en-us/azur...
3. Developing for queues using .NET
- docs.microsoft.com/en-us/azur...
Want to connect?
- Blog marczak.io/
- Twitter / marczakio
- Facebook / marczakio
- LinkedIn / adam-marczak
- Site azure4everyone.com - วิทยาศาสตร์และเทคโนโลยี
This is the clearest tutorial I've seen for Azure Queues, thanks!
Cool, thanks! Appreciated. :)
Adam is very good in explaining things, very good diagrams too. I am listening to all his videos here.
Great videos, I went through many of your videos on Azure and you sharing your knowledge with value information.
great video Adam! May I suggest you do a video explaining the similarities and differences between EventHubs, Service Bus Queues, Service Bus Topics, and Storage Queues?
Thumbs up for the clarity and simplicity in your content!
Thanks! I might, for new check this out docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services?WT.mc_id=AZ-MVP-5003556
Queues in a nutshell ! Now I feel like I can use this for my apps thanks again Adam!
Happy to help!
Excellent presentations and Top level teaching skill you have..
Very thorough anduseful. Thank you!
Glad it was helpful!
Your videos are fantastic, love the content
Adam is a rock star.
Thank you for sharing this demo.
My pleasure!
Clearly Explained. Waiting for other videos from you........
Thank you so much 🙂
Content is really nice, good work
Very useful tutorial on Queue Storage
Glad you think so!
Excellent! Thanks Adam
My pleasure!
Muito bem explicado, parabéns!
Obrigado!
Awesome! Thank you!
Your videos are awesome !
I appreciate that!
Very Nice Video Adam
Great video as always! I was wondering if you could do a series on Azure Synapse like you did for Databricks and ADF
Yea, this is one of the things I wanted to do for a very long time. Currently aligning my schedule for the next months so I'll check if I can include it :)
Hi Adam, again beautifully explained. However, I have one doubt. When we didn't delete the messages, why azure chose to not display the message in storage account? Even though it acknowledges the presence of those 4 messages. I am not able to understand the logic behind doing so.
HI Adam, great video. One thing, I do not understand how did you manage to do the fanout with logic apps ? That last part of video is a bit unclear to me, can you provide some explanation ?
I would like to improve my video teaching also. Your graphics and animation are great for explaining. May I ask what software you use for this? and also I was wondering if you do your own graphics or does someone else, it must take a lot of time? The quality of all aspects of your videos are really fantastic. Thanks
Thanks! That's just pure powerpoint. All diagrams are mine, created in visio and imported and animated. Screen is recorded using Camtasia. Thanks again :)
@@AdamMarczakYT Wow! That's an incredible amount of work, and it shows in the quality of your videos and content. Thanks!
You are fantastic. please make some videos on migration please.
Thank you! :D Noted!
I love your videos. Can you also talk about Data Lake tables?
Heya! Cheers! Do you mean DELTA Lake Tables on Databricks or Storage Tables on storage accounts?
I was under the impression that ADLS Gen 2 had blobs, queues, fileshares and tables. Is that incorrect? Thank you in advance for your reply.
@@atziazas Ach I understand now. Those Data Lake tables are same thing as storage tables. Only blob containers change to data lake file systems. Queues, File Shares and tables remain the same across Data Lake/Storage services. But yes I plan to make video on Table Storage service in near future.
Nice video. Would be interesting to see how it works with SQL Server Service Broker and retrieve the messages from there. I once did it with kafka and it would be nice to see how it works in Azure.
Thanks for the kind words. Not sure if your described scenario is supported this way.
Hi Adam, have you created any demo for 'Azure Service Bus'? If not then please make one
Service Bus is coming at some point :)
Can we use trigger when there are messages in a queue. Storage account is in same region and networking selected networks.
Thanks, how can we access and do various operations using the HTTP connector?
Awesome video :-) If I have access to someone else's storage queue through a connection string, should I then create my own storage queue in order to consume the given storage queue, or can I somehow "import" the already created queue?
Not sure I follow. It sounds like you want pub/sub model rather than queue. If someone processed event from queue then it's permanently delete so you can't copy anything from there.
Adam Marczak - Azure for Everyone It was poorly explained by me. I’ve been given a connection string to a Storage Queue from which I’m supposed to read the messages and store them when they appear minute by minute. My thought was to put them into Blob Storage, but I’m kinda confused on how to do it, since it’s not technically my Storage Queue. I was trying to follow some of your Logic App approach, but without luck. Hope it makes sense :-)
It makes sense now. Logic apps should work, so if they didn't then you made some mistake. In general storage account doesn't have to be yours for this to work. If you expect a lot of messages I'd advise to check Azure Function Apps as they are much cheaper at bigger scale. But I'd start with logic apps so you understand the concept. I'd probably delete logic app and try again, you probably made some mistake.
Adam pls share a video on service bus and a comparison among other messaging services
Eventually I'd love to do that, for now please check this doc docs.microsoft.com/en-us/azure/event-grid/compare-messaging-services?WT.mc_id=AZ-MVP-5003556 and this docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted?WT.mc_id=AZ-MVP-5003556
Is it possible to trigger an azure function using the queue?
Yes it is, here is the reference docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-storage-queue
Recorded on extreme low volume levels, but awesome.
Thanks! It's a 30 min intro so yeah, hopefully I can do more advanced videos in the future ;)
How can I do this in a C# console app? I reffer to subscribe and get the all messages
Check out official MS samples docs.microsoft.com/en-us/azure/storage/queues/storage-dotnet-how-to-use-queues?tabs=dotnet&WT.mc_id=AZ-MVP-5003556
Thank you for the helpful channel ^_^
Can you try to set better names, please? 'App1', 'App2', 'Demo1' could be 'CreateMessagesApp', 'ConsumeMessagesApp', 'StorageQueueDemo' :)
That is definitely a very good suggestion. Will start applying this immediately, especially since I had this conclusion recently as well as I've looked at my github with plenty of 'demo' apps. sO starting next episode this will be a standard. :)
10000000000 likes :)
I appreciate every single one of them :)
Thanks
Lol, dude justifies limit of message size by the idea of storing full data somewhere else(e.g. in DB) and the very first example of queue is to limit access to DB! Where in hell I supposed to store it stuff that doesn't fit message in this case?
up to 64k ... well, RIP Azure. Such stupid limitation makes it impossible to use in serious business cases
too fast man. I don't understand why you go so fast. you could be much more clear if you simply went slower in your explanations
Thanks for the feedback