News for hackers. Stuff that matters.
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by KellyCriterion on Monday November 16, 2026 @04:21AM (#50515626)
Denormalization & Joins are mainly a thing from 80-90s when diskspace & compute was expensive; today its easy just do denormalize everything and not use joins, since diskspace & RAM today is abundant.

(sure, not true for that one verylarge enterpriseDB at megacorpX, but in 95% of uses cases these topics do not matter anymore)

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by lompad on Monday November 16, 2026 @04:43AM (#50515772)
That makes it rather annoying to keep data consistent though, and tons of people just won't take enough care to properly update everything. Having had to deal with that kind of half-out-of-date mess, I'd rather not, tbh.
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by pak9rabid on Monday November 16, 2026 @01:23PM (#50520933)
See: MongoDB
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by oulipo on Monday November 16, 2026 @04:47AM (#50515795)
Not really, as the article mentions: if you simply denormalize everything, each time you need to eg update a user name, you suddenly have to update its whole posts and comments everywhere, making it something quite expensive
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by KellyCriterion on Monday November 16, 2026 @05:10AM (#50515936)
a) thats the reason why lot of platforms do not allow to change username after signup

b) absolutely manageable with a solid tooling (and honestly, in 99% of cases this event is trivial as most systems just do not hold enough data to make it like a "eeek this change will run for 3 days for that 1 user")

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by fauigerzigerk on Monday November 16, 2026 @07:11AM (#50516736)
>a) thats the reason why lot of platforms do not allow to change username after signup

Nor any of the other user data that is indexed with every single post?

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by KellyCriterion on Monday November 16, 2026 @07:43AM (#50517018)
If I look at my youtube comment notification, Id say propably not? (Timestamp belongs to a post as well as likes etc.?)
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by sgarland on Monday November 16, 2026 @08:45AM (#50517548)
Experience across multiple companies of varying size and maturity has proven to me that devs are incapable of doing the RDBMS’ job for it; there are always orphaned rows and referential integrity issues when FK Constraints get dropped.

Databases are hard. They’re also some of the best-tested code that exists, so maybe let them do their job.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by fallingbananna on Monday November 16, 2026 @05:12AM (#50515952)
This is true only if you have *very* specific data.
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by load-bearing on Monday November 16, 2026 @05:14AM (#50515967)
But why do it? You yourself are saying that it increases resource usage (which is mentality that left us with electron BTW), and creates additional difficulty with keeping data consistent. What's the upside?

I've never worked on anything, and probably won't ever work, that wouldn't fit in modern machines even in heavily denormalized forms, and have zero desire to do it just for consistency sake. 3NF or up, with very rare exceptions.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by weego on Monday November 16, 2026 @06:11AM (#50516287)
Your assumption that increased resource usage is single concept with one outcome and no nuance is entirely false (where do the problems of engineering a desktop app even overlap with row level schema planning in a database?)

The claim that is somehow causes data consistency issues also seems kind of unsubstantiated.

The upside is that when you model it correctly your data conforms to your domain and business in a way that makes every aspect of its use easier.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by lompad on Monday November 16, 2026 @09:55AM (#50518237)
> The claim that is somehow causes data consistency issues also seems kind of unsubstantiated.

Let me explain that part a bit more. If you have one application, developed by at most a handful of devs, there will not be any consistency issues. But add a few more applications and even a dozen devs (or just simply a decade of time and some staff changes), and there _will_ be misunderstandings/issues identifying the correct rows to update, with exact interpretation differing per application.

Congratulations, you now own a mess. Correcting this after the fact is a major effort.

If you're in 3NF this can't really happen - the exist once and only once. It's always clear which to update and nothing can be forgotten.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by williamdclt on Monday November 16, 2026 @11:22AM (#50519343)
while I mostly agree with you, you're opposing "teams who made mistakes while denormalising" with "teams who made no mistake while normalising". The biggest difference between these two scenarios isn't that one is using denormalisation and the other normalisation, it's that one made mistakes and the other didn't.

In real life, the teams working on a supposedly-normalised data schema will also make mistakes: they will model their domain incorrectly, have information duplication without realising it at first, different interpretation of the same data (accessing the same data doesn't mean they'll interpret it the same way... or that it even _can_ be interpreted in a consistent way if not modelled correctly).

I do agree that denormalisation increases the chances of that happening. But IMO, there's much more issues on data modelling than there is in denormalisation. If you have a solid model that is shared by everyone, you'll have much fewer issues even with denormalisation than if you have a not-solid model that is not-shared by everyone even with normalisation.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by RugnirViking on Monday November 16, 2026 @05:15AM (#50515972)
I do not agree, I believe normalization leads to a lot of other benefits like making you think about connections between data much more carefully, and thinking about what you need for each request. Denormalized tables have led way too many times in my experience to hapless developers fetching enormous amounts of data just to use a tiny amount far too often.

And db performance absolutely is an issue. Agents mess it up all the time on our codebases...

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by vidarh on Monday November 16, 2026 @05:16AM (#50515982)
Denormalization brings a complexity cost when updating to ensure integrity, though. And if storage and compute is cheap then you can easily get the benefits of denormalization without the downsides by keeping data normalized for consistency and instead build indexes to let you query it dernormalized when it makes sense.
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by fergie on Monday November 16, 2026 @05:43AM (#50516129)
> today its easy just do denormalize everything and not use joins

You _can_ take this approach on a read-heavy db, but depending on your usecase you are going to struggle with updates and writes.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by dam_jackalopes on Monday November 16, 2026 @02:15PM (#50521683)
I manage a pretty heavily denormalized data warehouse and it works pretty well for us, but we have individuals in the org making noise about wanting functionality to write back to the apps. Having to explain why this "simple" functionality will cause significant heartburn to our analytics team isn't at all fun.

At least I didn't design the thing so I have someone to shake my fist at.

Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by meindnoch on Monday November 16, 2026 @06:34AM (#50516428)
Or keep your data normalized, and maintain materialized views if and when they're needed.
Re:Do We Still Have to Denormalize? Have Your Schema and Sea... by cmiles74 on Monday November 16, 2026 @09:03AM (#50517697)
...And watch your updates take longer as they now update several columns over several tables instead of just one column in one table, and be sure to ensure that changes don't leave any data in an inconsistent state. I don't think this is an "enterprise" issue, it's about maintaining your data, and that effects 99% of applications that store data in a database.