Blog
DynamoDB schema patterns and single-table design guides.
-
DynamoDB Schema Migrations: The Guide Nobody Wrote
Schema changes in DynamoDB are possible - they're just different from SQL migrations. A practical guide to attribute changes, key structure changes, GSI additions, and ElectroDB versioning.
-
Single-Table vs Table-Per-Tenant in DynamoDB: The Real Tradeoffs
Why not just give each tenant their own table? A cost comparison, operational analysis, and decision framework for SaaS multi-tenant DynamoDB.
-
DynamoDB Single-Table Pattern: Social Media Feed
Fan-out on write vs fan-out on read - the two approaches to social feeds in DynamoDB, when to use each, and a production-ready schema with ElectroDB.
-
DynamoDB vs Postgres for E-Commerce: An Honest Comparison
I've built e-commerce backends on both. Here's when each wins - and when you'll regret the choice.
-
DynamoDB Tenant Isolation: Application-Layer vs IAM LeadingKeys
Two approaches to tenant isolation in DynamoDB - and when the complexity of IAM actually pays off over application-layer scoping.
-
ULIDs vs UUIDs vs Timestamps for DynamoDB Sort Keys
Why your sort key choice determines which access patterns are possible - and when to use ULIDs to get the best of both worlds.
-
DynamoDB Single-Table Pattern: E-Commerce Orders
A production-ready DynamoDB schema for e-commerce orders with 8 access patterns, status-based GSI, and full ElectroDB entity definitions.
-
When DynamoDB Single-Table Design Is the Wrong Choice
A DynamoDB advocate's honest take on when single-table design hurts more than it helps - and a framework for deciding.
-
DynamoDB Schema Pattern: SaaS Multi-Tenant
A complete single-table DynamoDB schema for SaaS multi-tenant apps. Access patterns, PK/SK design, GSIs, sample data, and ElectroDB entity code.
-
Why I'm Building a Visual DynamoDB Schema Designer
I've built production DynamoDB apps with 6+ GSIs per entity. The schema design process is still spreadsheets and guesswork. I'm fixing that.