News for hackers. Stuff that matters.

A comment on The GitHub Availability Report. Parent comment

Re:The GitHub Availability Report by dx034 on Thursday July 16, 2020 @03:31AM (#23856693)
It's actually an error I've seen multiple times in the past, and I'm not even working with databases full time. I do think it's surprising that no one had thought of implementing at least checks for these conditions.
[ Parent | on HN ]
Re:The GitHub Availability Report by capableweb on Thursday July 16, 2020 @04:11AM (#23856880)
Yeah, I think most people who touch/interact with backend/database code, even if not actually backend/DB developers, have a reaction nowadays to seeing auto-incremental IDs because it's famously hard to scale to any distributed architecture + introduces issues when you hit the limit.

Projects started in the last three years that I've collaborated/been part of have all ditched the auto incremental IDs.

[ Parent | on HN ]
Re:The GitHub Availability Report by baq on Thursday July 16, 2020 @04:36AM (#23856986)
Auto incrementing integer ids have some very desirable properties though. Not sure what you replaced them with.
[ Parent | on HN ]
Re:The GitHub Availability Report by dijit on Thursday July 16, 2020 @09:37AM (#23858809)
Something I see more and more is a primary key based on guid/uuid;

I'm not fully aware of the merits of either approach, so I'm just putting the info I have at hand out there.

[ Parent | on HN ]