# thinking-together

Steve Dekorte

08/10/2022, 3:31 PM
I thought this HN post on databases might be relevant to the future of coding:

Srini K

08/10/2022, 3:42 PM
Hmm seems to be from 2010? This structure seems to make sense for smaller teams / workloads

Kartik Agaram

08/10/2022, 4:03 PM

Tony Worm

08/10/2022, 4:13 PM
At the other end of scale, the (2013) article about how FB built their graph db on MySQL also hit HN today

Joakim Ahnfelt-Rønne

08/10/2022, 8:18 PM
The conclusion I take from this is that the RDBMS they used wasn't geared towards their use case back then, and they had to forego most of the advantages of the RDBMS as a result. It tells me that we need better RDBMS, and I will say that it has become a lot better in the years since then.


08/10/2022, 10:16 PM
For example @Joakim Ahnfelt-Rønne?

Joakim Ahnfelt-Rønne

08/11/2022, 6:03 AM
@wtaysom For example, I just - as a test - did
alter table (redacted) add column foobar bigint;
in a table with billions of rows in Postgres, and it was instant. It's worth noting that schema changes are also transactional in Postgres.


08/11/2022, 6:08 AM
My personal pain point is wanting to have multiple versions of the redacted table that I can modify independently and then merge later. I have managed to do this in Postgres, but it was not pretty.

Joakim Ahnfelt-Rønne

08/11/2022, 6:23 AM
That would be very handy for development.
Come to think of it, I was just invited to the beta of Xata, which has branching as an advertised feature. It didn't quite work for me when I tried it, but it's definitely an interesting goal. Edit: Turns out Xata only branches the schema, not the data.

Jack Rusher

08/11/2022, 7:50 AM
They basically re-invented the {Entity,Attribute,Value}/{Subject,Predicate,Object} style one sees in datalog/semantic web databases, but calling the Entity/Subject a "thing". Hopefully they kept improving it after 2010 until they realized they actually want triplicate indexing to allow good performance with complete query flexibility.