Stages of trusting DynamoDB BatchWriteItem:
1. Send 25 items
2. Get a 200 back
3. Assume all 25 landed
4. Rows go missing under load
5. Find UnprocessedItems
6. Retry them with backoff
A successful batch call doesn't mean every item was written. Which stage are you at?
1
112
Unpopular opinion: a DynamoDB Scan doesn't belong in a request path.
It reads the whole table, 1 MB per call, and you pay for every item read before any filter runs.
If a user is waiting on it, you need a Query, maybe on a GSI. Keep Scan for exports, backfills and admin tools.
87
Before you wire a Lambda to a DynamoDB stream in prod:
1. Pick the view type you need (KEYS_ONLY up to NEW_AND_OLD_IMAGES)
2. Make the handler idempotent. Retries happen
3. Cap retries and add an on-failure destination
4. Alert on iterator age. Records expire after 24h
2
83
Unpopular opinion: on-demand should be the default capacity mode for most new DynamoDB tables.
You don't know your traffic yet. A wrong provisioned guess either throttles or wastes money.
Measure real usage first. Switch to provisioned once the load is steady and predictable.
2
150
Before you import a CSV into a prod DynamoDB table:
1. Check every row has the key attributes
2. Map types (CSV has none)
3. Decide what a duplicate key does
4. Pace writes for live traffic
Dynobase's import wizard previews types, key coverage and conflict handling first.
1
2
95
Safer order when adding a DynamoDB GSI:
1. Confirm the Query pattern needs it
2. Create the GSI (existing items start backfilling)
3. Wait until IndexStatus is ACTIVE
4. Only then route traffic to it
CREATING ≠ ready. Queries on a still-building index fail or miss items.
1
111














