This is part 17 of a blog about some of the components on the Microsoft Azure platform PaaS, like app service, blob storage, Queue Storage, databases, databricks, Event Hubs, Functions, Gateways, Networking, IoT, Linux, containers, Azure Kubernetes Service, compute, security and many more. I am using all the letters of alphabet to do this. This is seventeen of twenty-six.
Q For Queue Storage
What is Azure Queue Storage?
Azure Queue Storage is a service for storing large numbers of messages. You access messages from anywhere in the world via authenticated calls using HTTP or HTTPS. A queue message can be up to 64 KB in size. A queue may contain millions of messages, up to the total capacity limit of a storage account. Queues are commonly used to create a backlog of work to process asynchronously.
Queue service concepts
The Queue service contains the following components:
- URL format: Queues are addressable using the following URL format:
https://<storage account>.queue.core.windows.net/<queue>The following URL addresses a queue in the diagram:
- Storage account: All access to Azure Storage is done through a storage account. For information about storage account capacity, see Scalability and performance targets for standard storage accounts.
- Queue: A queue contains a set of messages. The queue name must be all lowercase. For information on naming queues, see Naming Queues and Metadata.
- Message: A message, in any format, of up to 64 KB. Before version 2017-07-29, the maximum time-to-live allowed is seven days. For version 2017-07-29 or later, the maximum time-to-live can be any positive number, or -1 indicating that the message doesn’t expire. If this parameter is omitted, the default time-to-live is seven days.