3 ms·
I would never dare to suggest writing a new database in a professional context, even less during an interview. Probably as a joke at the coffee machine because
by speedgoose 7y ago
I would never dare to suggest writing a new database in a professional context, even less during an interview. Probably as a joke at the coffee machine because it's ridiculous but otherwise no.
It's so many distributed databases around there, no one is better than one good PostgreSQL for the majority of uses cases.
- bauerd 7y agoGoogle's requirements differ. Also if the interview question was about distributed systems, "I'll just use Postgres" is not super constructive
- speedgoose 7y agoGoogle has good in-house database software that fit their requirements. I wouldn't say that I can do better in an interview.
- bauerd 7y agoYes but that in-house database software did not fall from sky. Google developers wrote it. Remember their interview process is generalised. Even for candidates not expected to implement databases, they test for the awareness of tradeoffs posed by distributed databases: read-after-write/eventual consistency, linearizability, how many masters /quorum/leader election, etc. "Just use Postgres" does not demonstrate any of that, it's not what the interviewer was after.
- speedgoose 7y agoThat's true. We don't know how was the interview, perhaps it was about implementing a distributed database from scratch, perhaps it was about storing as many personal data as you can.
- inkeddeveloper 7y agoI would hope the answer to "how would you write a distributed database from scratch" isn't "I'd use PostgreSQL." Actually, I'd probably do the same.
- lcfcjs2 7y agoNot sure I would agree with this. People who say PostgreSQL for everything haven't ever needed a use case of Big Data, or quickly searchable datasets.