A new service has an unknown request rate.
Traffic may grow sharply, and the team does not want to continually tune capacity.
Which choice is most appropriate?
Compare DynamoDB On-Demand capacity for a workload whose request volume is difficult to predict.
Detailed explanation
A large reservation can cost too much while the initial load is low.
A large reservation can cost too much while the initial load is low.
On-Demand avoids advance capacity planning and charges according to request usage.
On-Demand avoids advance capacity planning and charges according to request usage.
Archive storage does not meet DynamoDB's low-latency access requirement.
Archive storage does not meet DynamoDB's low-latency access requirement.
DNS TTL does not change a DynamoDB capacity mode.
DNS TTL does not change a DynamoDB capacity mode.
Check official documentation
Compare the following points with the official documentation.
DynamoDB on-demand capacity modeの公式説明を確認する。
What to confirm
予測困難な負荷へオンデマンドキャパシティを選択できる。
Key points
- DynamoDB On-Demand
- Provisioned capacity
- Unpredictable workload
Notes
- Environment: AWS公式DynamoDBドキュメントの確認
- Confirm current AWS service behavior and pricing in the official documentation.
Foundation review
Capacity planning
On-Demand removes the need to predict an initial capacity level, while Provisioned can suit stable patterns.
Latency and cost
The mode choice should consider both response requirements and the expected request pattern.