accesspatterns.dev

The playground

Build any DynamoDB operation as a form or raw JSON and run it on the live engine, against a seeded MusicLibrary table. Read the response, the cost (Count, ScannedCount and ConsumedCapacity) and the latency of each call.

MusicLibrary: pk (pk), sk (sk) · 2 secondary indexes

Worked examples: An artist's catalogue · Every artist's profile · A genre, across artists · The same answer, by scan.

MusicLibrary

These rows are real and already here. Running an operation against them downloads a DynamoDB-compatible engine, about 850 KB, and executes it in this tab.

Try an example

One Query on the partition key returns the profile and every song together. No scan, no filter: the items were stored side by side.

pk(pk)
sk(sk)
name
country
type
title
genre
year

Run an operation to see the raw engine response.

table MusicLibrarykeys pk / skitems 47