3 ms·
I had to use it a few years back, for some data reporting that had been added to a project after the fact, and... I found it to be awful, because the task was v
by davidw 14y ago
I had to use it a few years back, for some data reporting that had been added to a project after the fact, and... I found it to be awful, because the task was very much a join-heavy operation. Something that would have been a breeze with Postgres, or even Mysql got turned into this big, ugly, heavy, slow process. I was not impressed, especially since the quantity of data in the DB was also something that could have very, very easily been handled by a very conventional relational DB running on a VPS, to say nothing of dedicated hardware.
Basically, they had chosen MongoDB due to the 'cool/new' factor, and it came back to bite them on the ass.
- einhverfr 14y ago>" I found it to be awful, because the task was very much a join-heavy operation. Something that would have been a breeze with Postgres, or even Mysql got turned into this big, ugly, heavy, slow process. " If you can't be assured of structure of data input, you can't reliably and gracefully transform that data on output. That's a pretty fundamental tradeoff between SQL and NoSQL (and historically between PostgreSQL and MySQL too).