Read and update session state by user ID with millisecond latency.
Traffic varies substantially and the team wants to avoid server management and a rigid relational schema.
Which data store is most appropriate?
Use Amazon DynamoDB for serverless key-value access with elastic capacity.
Detailed explanation
Athena queries S3 data and is not a millisecond single-key update store.
Athena queries S3 data and is not a millisecond single-key update store.
DynamoDB provides low-latency key access and managed scaling for variable traffic.
DynamoDB provides low-latency key access and managed scaling for variable traffic.
Archive storage is unsuitable for frequent, low-latency updates.
Archive storage is unsuitable for frequent, low-latency updates.
Redshift is an analytical warehouse rather than a session-state key-value database.
Redshift is an analytical warehouse rather than a session-state key-value database.
Check official documentation
Compare the following points with the official documentation.
Amazon DynamoDBのパーティションキー、オンデマンド容量、低レイテンシの公式説明を確認する。
What to confirm
運用分析・データウェアハウス・アーカイブと、単一キーDBを区別できる。
Key points
- DynamoDB
- Key-value
- Low latency
- On-demand capacity
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Access-pattern-first design
DynamoDB keys should be designed from the required Query and update patterns.
Capacity choice
Traffic predictability and cost determine on-demand versus provisioned capacity.