<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=931099456970389&amp;ev=PageView&amp;noscript=1">
bg-img11.jpg

Azure Queues

Steve Hughes
By Steve Hughes - August 21 2018

Azure QueuesIn today’s post I’d like to talk about Azure Queues. There are currently 2 queue options available – Storage Queues and Service Bus Queues. Let me tell you about the benefits of each, as well as the scenarios each are best for.

The first to Azure were Azure Storage Queues and are part of Azure storage. They feature a simple rest interface with Get, Put and Peak commands. Storage Queues are a reliable, persistent messaging mechanism for working within and between various services and environments.

Service Bus Queues are at the heart of the broader Azure messaging infrastructure which supports Pub Sub and other advanced patterns. These queues also have more support for integrating applications or parts of applications which can then span multiple communication protocols, data contracts, trust domains and network environments.

As Service Bus Queues were introduced later in Azure, they have significantly more options to meet solution application requirements that arise in your environment. Let’s take a look at 3 reasons for each that you may choose one over the other.   

Storage Queues – Use if:

  • you need to store over 80 GB of messages in your queue. A better option if you retain that history in your queue, know you’ll have a lot of messages sitting there or have larger messages.
  • you want to track progress of the messages, so if you need to know where it is in the process of the queue and track all that’s going on with a message.
  • you require service-side logs for all transactions against your queue.

Service Bus Queues – Use if:

  • you require first in/first out (FIFO) guarantees in your queue. There are many requirements around FIFO guarantees so Service Bus Queues are your best bet.
  • you require role-based access to your queues from different senders and receivers.
  • you need to be able to publish and consume batches of messages at a time.

There are many other differenences between these two products, but hopefully I’ve given you a starting point for selecting the best queue for your workload. If you have questions about queues or any other Azure product or service, we are your best resource. Click the link below or contact us—our Azure experts are here to help you wherever you are on your cloud journey.

New Call-to-action
bg-img14.jpg

Join Our Blog

Join other Azure, Power Platform and SQL Server pros by subscribing to our blog.

Leave a comment

Posts by Topic

see all

Recent Articles

Popular Articles