Dynamodb easy
A startup app has unpredictable and spiky traffic patterns. Which DynamoDB capacity mode is most appropriate for this use case?
- A Provisioned Mode: Manually setting strict limits to prevent high bills.
- B On-Demand Mode: A serverless 'pay-per-request' model that automatically scales throughput instantly to match traffic spikes.
- C Dedicated Hosting: Reserving a specific cluster of servers in the AWS Data Center.
- D Offline Mode: Caching all writes on the mobile device until the user is on Wi-Fi.
Answer: B. On-Demand Mode: A serverless 'pay-per-request' model that automatically scales throughput instantly to match traffic spikes.
On-Demand capacity is zero-maintenance. You don't need to predict your traffic. AWS handles the scaling automatically, and you only pay for the actual Read/Write requests you use. This is ideal for development or applications with unknown/highly variable traffic.
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?