An app needs single-digit millisecond lookups by key. Which store fits?
Why C is the answer
Amazon DynamoDB
DynamoDB is built for key-based, low-latency access.
In detail
- DynamoDB gives single-digit millisecond lookups by key.
- Design tables around your access patterns.
Use case
An illustrative scenario, not a real incident.
A game reads each player's profile by key within milliseconds, and DynamoDB suits that.
See it in different ways
flowchart TD
A{"Access pattern"} -->|"Analytics across columns"| B["Amazon Redshift"]
A -->|"Key lookups at low latency"| C["Amazon DynamoDB"]
A -->|"Files and a data lake"| D["Amazon S3"]
A -->|"Relational transactions"| E["Amazon RDS or Aurora"]mindmap
root((Stores))
Redshift
Complex analytics
DynamoDB
Fast key lookups
S3
Data lake
Athena
SQL on S3sequenceDiagram participant P0 as App participant P1 as DynamoDB P0->>P1: Get item by key P1-->>P0: Item in milliseconds
Key point: DynamoDB serves key-based, low-latency access.
Why the other options are wrong
- A. Amazon Redshift, with a query for each lookup
- Redshift is not for key lookups.
- B. Amazon Athena, with a query for each lookup
- Athena is not for key lookups.
- D. Amazon S3 Glacier Deep Archive
- Deep Archive takes hours.