Dynamodb easy
As a DynamoDB table grows from 1GB to 100TB, how does AWS manage the underlying physical storage?
- A It requires the user to manually migrate the data to a larger cluster type.
- B It automatically shards (splits) the data across an increasing number of physical servers (Partitions) behind the scenes, ensuring performance remains constant.
- C It slows down writes for older data to prioritize new data on the SSDs.
- D Data beyond 1TB is automatically moved to cold storage (S3 Glacier).
Answer: B. It automatically shards (splits) the data across an increasing number of physical servers (Partitions) behind the scenes, ensuring performance remains constant.
DynamoDB is designed for 'unlimited' storage. Once a partition reaches its size (approx 10GB) or throughput limit, AWS splits it. This management is entirely transparent to the developer—the API remains the same regardless of table size.
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?