Dynamodb easy
Which set of characteristics best describes the DynamoDB data architecture?
- A Relational: Focused on normalizing data across multiple tables with foreign keys and ACID JOINs.
- B Schema-on-Read: It is an object-store like S3 where data cannot be indexed but is highly durable.
- C NoSQL Key-Value and Document: Data is stored as semi-structured Items (JSON-like) that can be accessed by a primary key or secondary indexes.
- D Graph: Designed primarily for traversing complex many-to-many relationships using edge-weights.
Answer: C. NoSQL Key-Value and Document: Data is stored as semi-structured Items (JSON-like) that can be accessed by a primary key or secondary indexes.
DynamoDB is a schema-less (at the attribute level) NoSQL store. It provides the low-latency Key-Value speed while supporting complex nested document structures, making it versatile for both metadata and large JSON payloads.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- DynamoDB has a strict 400KB limit on the size of a single item. What is the recommended design pattern if you need to store larger documents (e.g., 5MB PDFs)?
- What is the primary role of the 'Partition Key' in ensuring DynamoDB's infinite horizontal scalability?
- Why is the `Query` operation generally preferred over `Scan` for production workloads in DynamoDB?
- DynamoDB is a 'fully managed' serverless database. What is a primary operational benefit of this model for an engineering team?
- In 'Provisioned Capacity' mode, how is the performance budget of a DynamoDB table defined?
- When would an architect choose to implement DAX (DynamoDB Accelerator) in front of an existing DynamoDB table?