Why this matters
- VaultCommerce's high-write order-events service outgrew Postgres connection limits — DynamoDB scales partitions horizontally when keys are well distributed.
- You cannot ad-hoc query arbitrary attributes; the primary key (and indexes) define every read path upfront.
- Single-digit millisecond latency comes from predictable key lookups, not from scanning tables.
Tables, items, and attributes
{
"PK": "USER#42",
"SK": "ORDER#2026-0042",
"customerName": "Alice Chen",
"totalAmount": 129.99,
"status": "SHIPPED",
"lineItems": [
{ "sku": "SKU-8842", "qty": 1, "price": 89.00 }
]
}
Building blocks
- Table — collection of items; no fixed schema beyond the key definition.
- Item — one record, up to 400 KB including attribute names and values.
- Attribute — name-value pair; types include string, number, boolean, list, map, set.
- Primary key — partition key alone, or partition + sort key (composite).
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 3 sections
- Partition and sort keys
- When DynamoDB fits VaultCommerce
- Consistency model
Test yourself
Answer these before moving on — recall is what makes it stick.