Azure Queue Storage

Introduction

Queue Storage is a service for storing large numbers of messages (for the purpose of processing them later asynchronously)
- Messaging for applications
- Enqueue and dequeue semantics
- Parallel clients
Queue Storage is similar to the concept of queue data structure for storing messages in ‘FIFO (First In, First Out)’ rule
A queue may contain millions of messages (up to the total capacity limit of a storage account)
Access: REST-based GET/PUT/PEEK interface (can be accessed messages from anywhere in the world via authenticated calls using HTTP or HTTPS)
Limitations:
- A queue message can be up to 64 KB in size
- messages in a queue are not replicated anywhere (means there is only one copy of the message)

Commonly used to create a backlog of work to process asynchronously
To exchange messages between components
Decoupled and independent components rely on asynchronous message queuing
Multiple services need to communicate with each other by messaging
Connecting multiple components of same application (by inter-component messaging)
Can be used for emails (email sending feature of an application)
Simple alternative of MSMQ, Azure Service bus etc.

Azure Queue service components and thier relationship diagram

Azure queue storage - create queue