Querying & Sorting
Reads are where the bill gets written. Query targets one item collection by key;
Scan reads the whole table. Reach for Scan with a filter — the SQL instinct —
and you pay for every item read, not the few you keep. That's the classic footgun.
This section is about reading efficiently: using the key to do the work, paging correctly, and ordering results with the sort key instead of in-memory sorting.
0 of 10 readQuiz
Start with Query vs Scan — it's the decision the rest depend on.
Try DynoTable to run these queries against a live table.