4 ms·
>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
by veave 3y ago
>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?
- joshstrange 3y agoSee "Single Table Design" which I talked about in this comment above: https://news.ycombinator.com/item?id=37093357 https://news.ycombinator.com/item?id=37093357
- deely3 3y agoAnd if you don't want to spend money, you can get basic idea from this article: https://www.alexdebrie.com/posts/dynamodb-single-table/ https://www.alexdebrie.com/posts/dynamodb-single-table/
- newlisp 3y agoDuplicate data to avoid joins, use serializable transactions to update all the duplicated data.