Playground

Explore how effect-dynamodb composes DynamoDB keys and generates query parameters. Select a scenario, adjust the schema config and entity attributes, and see the generated keys and API parameters update in real-time.

ScenarioTask Manager — Basic single-entity with primary + one GSIHR System — Multi-index with collection for cross-entity queriesE-Commerce — GSI overloading with price range and category queriesCricket Match — Complex key patterns with clustered collections

Schema Config

Name

Ver

Casinglowerupperpreserve

Entity Attributes

taskId (string)

projectId (string)

status (string)

title (string)

Generated Keys

schema prefixentity/collectionattribute values

pk$taskapp#v1#task#task-001

sk$taskapp#v1#task

gsi1pk$taskapp#v1#task#proj-42

gsi1sk$taskapp#v1#task#active

KeysPutItemQuery

{
  "pk": "$taskapp#v1#task#task-001",
  "sk": "$taskapp#v1#task",
  "gsi1pk": "$taskapp#v1#task#proj-42",
  "gsi1sk": "$taskapp#v1#task#active"
}

How It Works

The playground demonstrates the key composition engine at the heart of effect-dynamodb:

1. Schema prefix — Every key starts with $<schema>#v<version> to namespace ORM-managed keys
2. Entity type — Identifies the entity within the single-table design
3. Composite attributes — Your domain values appended to the key in declaration order

Keys are composed from the indexes config on your Entity declaration. The playground runs the same pure functions as the library — DynamoSchema.composeKey, KeyComposer.composePk, KeyComposer.composeSk — directly in your browser.