Dynobase (@dynobase) header
Dynobase (@dynobase) profile picture

Professional GUI Client for DynamoDB https://teapawt.net/t.co/nqS5b8GVKr

Joined January 2020
Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)Photo by Dynobase (@dynobase)
What actually happens when you call UpdateItem in DynamoDB? 🧵 Five steps, and two of them surprise most people.
1
1
32
5. Every index whose keys or projected attributes changed gets written too, and those writes cost capacity as well. If Streams are on, the change is recorded there. Tip: ReturnValues UPDATED_NEW hands you the result without a second read.
1
4
Which of these bit you first? In Dynobase, the Operation Builder shows the generated update code and conditions before you run the write.
4
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.
2
80
What's the first DynamoDB habit you break when a new teammate joins? Mine: assuming UpdateItem only updates existing items. Without a condition, it creates the item if the key is missing. What's yours?
77
Unpopular opinion: every production DynamoDB table should have deletion protection on. It's free. It's one setting. And it turns "oops, wrong account" into an error message instead of an incident. A prod table shouldn't be one API call away from gone.
72
35 days. That's the longest window DynamoDB point-in-time recovery can restore from, down to the second. The catch: PITR is off until you turn it on, and a restore always lands in a new table. Enable it before the bad deploy, not after.
1
103
Stages of DynamoDB "we'll fix the key later": 1. Ship with a busy-friendly PK 2. Traffic grows 3. One hot key 4. Throttles in prod 5. "We'll shard next sprint" 6. Next sprint ships features instead Which stage are you stuck in?
2
154
Myth: you can add a local secondary index later. You can't. LSIs are chosen at CreateTable. After that, the only option is a new table (or a GSI, which is a different tool). Need another sort-key pattern on an existing table? Plan a GSI — or migrate.
1
65
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
109
10 GB. Max size of one DynamoDB partition that holds a local secondary index. An LSI lives on the same partition as the base item. Grow past ~10 GB and writes that enlarge it start failing. Watch partition size, not just RCU/WCU.
1
66
Myth: ConsistentRead on a Scan makes the whole table strongly consistent. Wrong. It only applies within each partition page. Across pages you can still see mixed old and new versions. Need a true snapshot? Use Export or PITR — not ConsistentRead Scan.
60
Unpopular opinion: most DynamoDB throttling is a key-design problem, not a capacity problem. Raising provisioned WCU won't help if every write hits the same partition key. Fix the key (or shard it) before you buy more throughput. Agree?
1
4
125
A failed ConditionExpression still costs write capacity. The reason? DynamoDB reserves write units for the item size before it checks the condition. A 3 KB PutItem that fails still burns 3 WCUs. Watch conditions that fail often — you pay for rejected writes.
51
Nested maps and lists are painful in a flat DynamoDB grid. Expand a cell, lose the shape, hope you didn't break it. Dynobase's JSON editor opens the same item as JSON. Edit the nested structure, then save.
64
1 MB. A single Query or Scan response is capped at 1 MB (and by Limit if you set one). Large items → fewer items per page. Always loop on LastEvaluatedKey.
48