Re:The Part of PostgreSQL We Hate the Most (Multi-Version Co...
by inferiorhuman on Thursday April 27, 2023 @01:24AM
(#35723634)
Mongo was so comically bad. I remember trying to sort through a slow query and thought: ah ha! I'll just add an index. Unfortunately on that version of Mongo, creating an index would occasionally just crash the server process.
I think Mongo became popular because it's ad tech and those guys knew how to be buzzword compliant. JSON-esque documents are one thing, but Mongo is Javascript to the core. All of a sudden your JS devs don't have to learn SQL they can just shit out some queries in javascript. Of course that came with some pretty severe drawbacks.
Re:The Part of PostgreSQL We Hate the Most (Multi-Version Co...
by The_Colonel on Thursday April 27, 2023 @04:18AM
(#35724852)
As I remember, MongoDB got popular before node.js, so there wasn't really a lot of backend JavaScript developers out there to make a difference.
We first used Mongo ~11 years ago with Java. For us the benefit was that we could dump unstructured data into it quickly, but still run queries / aggregations on it later.
Re:The Part of PostgreSQL We Hate the Most (Multi-Version Co...
by orthoxerox on Thursday April 27, 2023 @04:19AM
(#35724856)
My favourite story about MongoDB is that it was so bad and popular at the same time that when a competitor developed a wire-compatible database that was miles better they simply bought it and released it as the next version of MongoDB.
Re:The Part of PostgreSQL We Hate the Most (Multi-Version Co...
by pier25 on Thursday April 27, 2023 @09:28AM
(#35727797)
which db was that?
Re:The Part of PostgreSQL We Hate the Most (Multi-Version Co...
by orthoxerox on Thursday April 27, 2023 @09:36AM
(#35727902)
I think I meant WiredTiger.
Honestly I think it only gained traction because many Node devs refused to learn SQL and the document model is familiar because it's closer to JSON data.
These days Mongo is good but that wasn't the case back 10+ years ago.