Microsoft Azure Data FundamentalsDescribe how to work with non-relational data on AzureMedium
A developer is creating an application that requires a simple key-value store to maintain user preferences and configuration settings. Each item will have a unique identifier (key) and associated attributes (values). The schema for these attributes might vary slightly between different types of items but is generally flat. High throughput and low latency are important, but global distribution is not a primary concern. Which Azure non-relational data service is the most cost-effective and suitable choice?
- AAzure Data Lake Storage Gen2
- BAzure Blob Storage
- CAzure SQL Database
- DAzure Cosmos DB (Table API)
Show answer & explanationAnswer & explanation
Correct answer: D. Azure Cosmos DB (Table API)
Azure Cosmos DB's Table API provides a key-value store compatible with Azure Table Storage. It's suitable for simple, structured data with varying schemas, offering high throughput and low latency at a lower cost for scenarios where global distribution of a full Cosmos DB account isn't required.
Why the other options are wrong
- A. Azure Data Lake Storage Gen2 is for big data analytics, not a simple key-value store for application settings.
- B. Azure Blob Storage is for unstructured object storage, not a key-value database.
- C. Azure SQL Database is a relational database, over-engineered and more expensive for a simple key-value store with flexible schemas.
Azure Cosmos DB (Table API)
A NoSQL key-value database service within Azure Cosmos DB that provides high throughput and low latency for structured, non-relational data, compatible with Azure Table Storage.
- Key-value store for structured, non-relational data.
- Compatible with Azure Table Storage SDKs.
- Offers schema flexibility, allowing attributes to vary.
- Provides high throughput and low latency, cost-effective for simple scenarios.
Memory trick: For simple 'Keys' and 'Values', a 'Table' is perfect, like a well-organized index.