Microsoft Azure Data FundamentalsDescribe core data conceptsHard
A global logistics company needs to store tracking information for millions of packages. Each package's tracking status changes frequently, and the data for each package (e.g., current location, delivery attempts, customs information) can have a highly variable and evolving structure. The system requires high throughput for updates and low latency for retrieving a package's current status. Which data model is MOST appropriate for this scenario?
- AColumn-Family Data Model
- BDocument Data Model
- CRelational Data Model
- DGraph Data Model
Show answer & explanationAnswer & explanation
Correct answer: B. Document Data Model
The Document Data Model excels at handling data with variable and evolving structures, like package tracking details, offering schema flexibility and high throughput for updates, which is crucial for dynamic logistics data.
Why the other options are wrong
- A. Column-family models are good for sparse, high-dimensional data, but a document model fits the 'variable and evolving structure' requirement more directly for a single entity like a package.
- C. Relational models require a fixed schema, which is not suitable for highly variable and evolving package tracking data.
- D. Graph models are for complex relationships, not the primary need of flexible, individual package tracking records.
Document Data Model
A NoSQL data model that stores data in document-like structures, typically JSON or BSON, allowing for flexible and schema-less data representation.
- Each document is self-contained and can have a different structure.
- Ideal for semi-structured data and rapidly evolving application requirements.
- Offers high scalability and performance for read/write operations.
Memory trick: Documents for Dynamic Detail, Not Rigid Rows