4 ms·
Relational vs non-relation is one of the biggest misconceptions about NoSQL Data is usually relational, there's no getting away from that just because of the d
by thdxr 5y ago
Relational vs non-relation is one of the biggest misconceptions about NoSQL
Data is usually relational, there's no getting away from that just because of the database you use. NoSQL can manage all kinds of relations, just with an extremely different approach.
If you're interested in learning how this works instead of repeating the tired meme of "mongodb lol" checkout Alex Debrie's book on DynamoDB and Rick Houlihans YouTube content.
I also wrote a brief thread about this on Twitter: https://twitter.com/thdxr/status/1394903426023272452?s=19 https://twitter.com/thdxr/status/1394903426023272452?s=19
- greymalik 5y agoBook link for the lazy: https://www.dynamodbbook.com/ https://www.dynamodbbook.com/
- bokwoon 5y agoI've seen a very good article on this: https://www.trek10.com/blog/dynamodb-single-table-relational-modeling https://www.trek10.com/blog/dynamodb-single-table-relational.... It's an insightful dive into how KV stores can model relational data. However I also feel that these 'NoSQL can do relational modelling!' proponents are kind of hijacking the term: a relational model is understood to be based on relational algebra, and DynamoDB's Everything is One Big Table design ain't it. NoSQL can model relational data, but it is not a relational model (as understood by E.F. Codd). Also, NoSQL data access patterns are pretty much set in stone, which is kind of what the relational model explicitly avoids.