Microsoft Azure Data FundamentalsDescribe how to work with non-relational data on AzureMedium
A company is developing an IoT solution that collects telemetry data from thousands of devices. Each device sends a small message (e.g., sensor readings, status updates) every few seconds. These messages need to be temporarily stored in a buffer before being processed by a backend service. The solution requires high throughput for message ingestion and guaranteed delivery to the processing service. Which Azure non-relational service is most suitable for this message queuing scenario?
- AAzure Data Lake Storage Gen2
- BAzure Cosmos DB
- CAzure Queue Storage
- DAzure Blob Storage
Show answer & explanationAnswer & explanation
Correct answer: C. Azure Queue Storage
Azure Queue Storage is a messaging service designed for storing large numbers of messages that can be accessed from anywhere in the world via authenticated calls. It provides a robust, scalable, and durable message queue solution ideal for buffering high-throughput IoT telemetry data for later processing, ensuring guaranteed delivery.
Why the other options are wrong
- A. Azure Data Lake Storage Gen2 is for big data analytics and data lakes, not for temporary message buffering with guaranteed delivery between application components.
- B. Azure Cosmos DB is a globally distributed database, while it can handle high throughput, it's overkill and more expensive for simple message queuing compared to Queue Storage.
- D. Azure Blob Storage is for storing large unstructured binary data, not for message queuing or guaranteed delivery of individual messages in a queue.
Azure Queue Storage
Azure Queue Storage is a service for storing large numbers of messages. It enables asynchronous communication between application components, decoupling them and improving scalability, reliability, and fault tolerance.
- Provides reliable, persistent messaging between application components.
- Supports millions of messages with sizes up to 64 KB per message.
- Cost-effective for high-volume message scenarios.
- Messages are delivered at-least-once, with visibility timeouts for processing.
Memory trick: Think 'Queue Storage: Q for Quick, Q for Quantity, Q for Queuing'.