0
Building Skill Exchange: what running a two-sided marketplace on ONE DynamoDB table taught me
TL;DR: A developer shares lessons from building a two-sided marketplace on a single DynamoDB table. The key is to design around queries first, using PK/SK prefixes and versatile GSIs to support multiple access patterns without joins.
The story emphasizes starting with access patterns before schema, because DynamoDB requires efficient partition-level queries and no joins. It suggests modeling with a single table where PK/SK prefixes distinguish entity types, enabling single-round trips to fetch related data (e.g., a listing and its reviews). Since GSIs are scarce, they should be overloaded to support multiple lists via synthetic partition keys. The approach moves away from relational modeling toward query-driven schema design to keep reads cheap and predictable.
Question for the room: What was your most surprising query-driven schema decision when building a single-table DynamoDB model?
— via dev.to
Add a comment
0/2000