Real-world scenario
A new mobile app needs a low-latency user profile store. DynamoDB's single-digit millisecond reads and pay-per-request billing fit the workload.
By the end you can:
Follow the request/data flow through the architecture.
Work through each concept and mark it understood. This unlocks the knowledge check.
Fully managed serverless NoSQL key-value/document database.
Why it matters
Single-digit-millisecond latency at any scale with no servers.
When to use it
Use for known access patterns at high scale. Avoid for ad-hoc analytical queries (use Athena/Redshift).
Example
table.put_item(Item={
"pk": "USER#42", "sk": "PROFILE",
"name": "Ada", "plan": "pro"
}) # design around access patterns, not normalized tablesGotcha (exam trap)
You model around access patterns, not relations. A poor partition key creates "hot partitions" that throttle.
Use the simulated AWS console below to complete each mission step. No real AWS account is required.
Create a DynamoDB table named "Customers" with partition key "customer_id".
Put a JSON item: {"customer_id":"c-900","region":"us-east-1","tier":"premium"} into the Customers table.
Bleepx skills build on each other. Continue your learning path across Query, Lab, and Cloud.