Re:Data-Oriented Design
by hu3 on Tuesday July 04, 2023 @11:29PM
(#36595222)
> Reduced column bloat, easy reusability, easy reporting and data extraction, ease of bulk transformation (especially stream processing)
Respectufully, this sounds like just a bunch of words with no explanation. To pick one topic from that, reporting is easier when you don't have to JOIN more tables, not harder. Same for data extraction. And how can bulk transformation be harder just because a column is where it would intuitively reside and not in another table who knows where?
> I have to reject outright the suggestion that joins are unnatural in a relational database.
I'm afraid you misunderstood. It's unnatural to me, the developer, not to the database, to spread closely related columns accross different tables.
And "tables that grow indefinetly" is doing a lot of heavy lifting for those arguments. Most tables don't grow indefinetely.
Like I said, smells like premature optimization. I optimize for humans first.
Respectufully, this sounds like just a bunch of words with no explanation. To pick one topic from that, reporting is easier when you don't have to JOIN more tables, not harder. Same for data extraction. And how can bulk transformation be harder just because a column is where it would intuitively reside and not in another table who knows where?
> I have to reject outright the suggestion that joins are unnatural in a relational database.
I'm afraid you misunderstood. It's unnatural to me, the developer, not to the database, to spread closely related columns accross different tables.
And "tables that grow indefinetly" is doing a lot of heavy lifting for those arguments. Most tables don't grow indefinetely.
Like I said, smells like premature optimization. I optimize for humans first.