3 ms·
I see so reference data that you want included in an object for which you're willing to pay the performance overhead of a join rather than denormalize across ma
by redwood 5y ago
I see so reference data that you want included in an object for which you're willing to pay the performance overhead of a join rather than denormalize across many object representions in your database. This model has some downsides when it comes to reasoning about scale and denormalization isn't necessarily a consistency quagmire when you can use transactions to keep multiple objects in sync. More generally you can absolutely do this types of queries in modern data systems whether or not they are "relational".
- marcosdumay 5y agoYeah, I guess I should retract my claim that people aren't claiming it's useful for relational data anymore. Anyway, I was focusing on invariants. But yes, destroying your performance every time you need an atomic change or joining values also makes it bad for relational data. That doesn't mean it's useless, just that it should not be used on the most common problem people have with their data.