Azure Queue Storage Reviews

1. Easy to implement with the services running in Azure

2. Supports HTTP and HTTPS authentication

1. Message in the queue will stay for only 7 days

2. Difficult to integrate with the service outside the Azure environment

The overall options provided by azure for the different types of data that could be put into this storage type is just excellent, not only this but it can also pull data from other sources within the azure active directory like event hubs or service buses based on some custom triggers using function apps. Since Azure provides the product, the charges applied are for whatever you use, and the period you use it for and gives us transparency using tags to the resources we create every month the spendings occurring on each of them

The overall complexity of connecting different queue storage accounts with external APIs is a little complex as per my opinion, which makes the product to be used in more of an Enterprise Environment by a professional having an advanced level of knowledge about azure and storage accounts

I would strongly recommend this product to be used for enterprise solutions on the cloud with strict budgets being followed and the need for transparency for cost trends

We can use the azure queue storage to store data coming from the azure service bus into the queue whenever the subscriber that needs to process the data is not available and retry fetching the same data from the queue and push it after every one hour to the subscriber, so basically using the queue as a temporary placeholder for the unprocessed data to be stored at and using this we were able to know about the cost trends for different types and sizes of data being pushed into the system and reduce the same by conversion of data into another type

I am personally using this service of Microsoft for my personal purpose as well as my office purpose. it gives me the freedom to store my message for a long period of time and I can see all of them by filtering process from anywhere anytime. I am using this service as a cloud-based platform for my message management and it is really working well till now. it creates filtered message charts for you. it deletes the unwanted message automatically if you specify proper wording to them. you can select your preferences by serverless 360 easily. very cheap in price.

it only good for a small message storage system because its real-time capacity for messages is up to 64kb. you can not store messages larger than this size. if you are not managing it regularly then your messages will come randomly that's the only problem that I face up till now but you can find out your valuable message by filtering. Microsoft provides better security always.

one should use this service of microsoft. cost wise very cheap and you can do multiple tasks with it you can see your message form anywhere in the world.

I am using mostly it to keep my message safe and secure for a longer period of time.

What I love is my personal file storage design, because it prevents me from disturbing the order I have chosen.

Disorder, people who do not follow the established order. I do not like disorder. It is the poor organization of messages.

It's a good method to be able to organize the messages, and to distribute them.

The advantage is that it follows its course in the order you have established. The order is followed. The line is respected. The thread of the line follows its course. The stock of messages is well organized.

I closed worked with Azure Storage queues. Even with no prior knowledge on the subject, i was able to read about and MSDN documentation was really helpful. It has tight integration with Azure functions and really saves on storage. Easy to implement with Microsoft Stack

Nice integration with Azure functions, however, I felt SAS token reset policies should be a little easier to handle. The Azure Queue explorer tool is also kinda slow, makes system hangs for a bit. We need a more stable version of this tool. VSTS should also have tight integration with storage-explorer.

Document storage and CRM storage.

It is the easiest way to saving large messages.it facilitate us in using messages anywhere

Our saved messages expires in 7 days as default.

It is an efficient and effective way of saving messages and use it anywhere in the world

I was facing lack of saving large messages.

.The different worker nodes makes it very reliable as no messages are lost and it can take the lost messages from the exact place and transits it

No transactional behavior and atomicity when sending or receiving messages from a queue

Go for it if you have to send alert messages, promotional messages

We are sending alert messages to our customers using this at once and we have noticed the system is fault tolerant

It can store multile messages which can be accessed through HTTP / HTTPS.

Queue Message size should be increased more than 64 kb.

Excellent Queuing, Passing message to other Azure Users. Load Balancing.