Microsoft Flow / State Machine / Azure Storage Queues (6/8)
Updated: Jan 29, 2019
Queues are providing us with enterprise software capabilities at our fingertips for a very reasonable price. The impact on the solution stability of this robust, highly scalable and easy to use lego brick, is insane.
What is Azure Queue Storage?
Azure Queue storage is a service for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls using HTTP or HTTPS. A single queue message can be up to 64 KB in size, and a queue can contain millions of messages, up to the total capacity limit of a storage account. Content brought to you by Microsoft.
What's the benefit of Azure Queue Storage in Flow?
Azure Storage Queues are a very cost effective solution. These connectors belong to the set of Standard Connectors and don't require a premium plan for each user. As for example the HTTP connectors will require starting from spring 2019. This makes a huge difference in price, as 1GB of queue storage costs about $0.07 and max message size is 64k.
JSON used as a data exchange format for the state object, is very flexible and can basically contain any data, even binary.
So, what Queues do we need actually need for our solution? Basically every Flow get's a Queue. So we are talking about a 1:1 mapping between Flows and Queues.
I'm sleeping so much better, since I know, that my json messages are safe and in case, smth would go wrong beeing protected by automated and intelligent failure recovery.
The little downside of asynchronous processing causing delays in processing is acceptable for most processes, and with a better plan we can make them act faster. Our customers are processing thousands of messages since months and there wasn't one, not handled correctly. ;-)
Please find more information on the topic here:
There is a lot more of content available to you: