Hacker News Reader

>Design your application's hot path to never use joins. Storage is cheap, denormalize everything and update it all in a transaction. It's truly amazing how much faster everything is when you eliminate joins.

Anybody has documentation about this with examples?

View on HN

See "Single Table Design" which I talked about in this comment above: https://news.ycombinator.com/item?id=37093357

And if you don't want to spend money, you can get basic idea from this article: https://www.alexdebrie.com/posts/dynamodb-single-table/

Duplicate data to avoid joins, use serializable transactions to update all the duplicated data.

Reply on news.ycombinator.com