8 ms·
OK I'll say it... Your friend chose wrong. HORRIBLY wrong. I have a lot of experience with both Postgres and Cassandra and the fact that your friend chose Cassa
by haggy 8y ago
OK I'll say it... Your friend chose wrong. HORRIBLY wrong. I have a lot of experience with both Postgres and Cassandra and the fact that your friend chose Cassandra despite their data model being relational AND having high consistency requirements shows that they chose Cassandra for the wrong reason(s).
Before you come back saying something about scalability, I've run both databases at way above average scale so what you choose should come down to what you need, which is not what was done in this case (your friend)
- mekoka 8y agoI think his comment was mostly about the fact that you can learn a lot about relational databases by reading Postgresql's source. He did say at the height of NoSQL hype. To me, that choice of words gives subtle hints as to the historical context and a disclaimer about the pertinence of that decision. Thank you for your input though, it provides food for thought for the next person mulling over a similar decision.
- int_19h 8y agoIt sounds like his friend didn't choose anything, his bosses did.
- macspoofing 8y ago>Your friend chose wrong. HORRIBLY wrong. Yeah, obviously. Also, he didn't choose anything. The tech stack was mandated on him.
- nickpeterson 8y agoSometimes the best way to learn the value of something is to try really hard not to use it.