Even mongo only got a lot of people excited because they had hot girls on the stalls in the conferences. That i think was a master stroke in marketing to nerds. of course later on they improved the product as well, but initially it was a buggy mess and should not have survived the first few years.
The one constant in my career has been mongoDB -- specifically, projects to replace it with a relational database after a deployment had failed to deliver any of the expected benefits, and introduced unforeseen downsides that had become untenable. Mongo has literally never come up in any context for me where it wasn't either already, or eventually, slated for retirement.
I absolutely don't doubt a document store including mongo is an ideal solution for certain specific applications. I just haven't come across one yet personally. For me personally, I would use Postgres for most things and JSONB columns for document-like things until I found a reason to change.
unless you have a really strong unique selling point, it's hard to sell a DB that's only available as a service and not runnable locally?
They used to provide a Docker image for local dev but that was it AFAIK.
as a saying goes from crypto crowd: not your keys, not your coins.
same might apply to data: not your server, not your data.
My take: the industry is so set on SQL as as standard that FQL made Fauna a hard sell for production applications. Also, the pricing was quite steep.
Even mongo only got a lot of people excited because they had hot girls on the stalls in the conferences. That i think was a master stroke in marketing to nerds. of course later on they improved the product as well, but initially it was a buggy mess and should not have survived the first few years.
The one constant in my career has been mongoDB -- specifically, projects to replace it with a relational database after a deployment had failed to deliver any of the expected benefits, and introduced unforeseen downsides that had become untenable. Mongo has literally never come up in any context for me where it wasn't either already, or eventually, slated for retirement.
I absolutely don't doubt a document store including mongo is an ideal solution for certain specific applications. I just haven't come across one yet personally. For me personally, I would use Postgres for most things and JSONB columns for document-like things until I found a reason to change.
5 replies →
i worked at MongoDB for nearly 10 years... when the heck did they have booth babes at conferences?
hyped != viable