Marketing. They marketed the hell out of it. Most developers I know have MongoDB mug.
> Lately I haven't read any news about a company migrating to Mongo, but rather most were either departing from mongo
They had some strange defaults to start with (to give them serious advantage in small silly benchmarks) like un-acknowledged writes. Yes you read that correctly, for years their default configuration was to throw write requests over the fence and assume they succeeded.
There are some horror stories of people's databases becoming silently corrupted. Those corrupted databases were then backed up and back ups were corrupted.
Eventually they had fixed their defaults but their reputation as an engineering company went down the hill ( I speak for myself here mostly).
From my experience a lot of people using MongoDB don't know what they are using. To them 'unacknowledged writes' and 'database level locks' sounds like Latin. They see short examples, cool mugs, other cool kids talking about how easy MongoDB is and they start using it.
or - mongo is great for some problems and not so great for other problems. if there is one thing you can figure out hanging out on HN long enough - it's cool to hate on mongodb
Tens of thousands of computer geeks all randomly chose to hate a product. Clearly a coincidence or unlucky alignment of stars, nothing to do with said product, of course.
It could just be the case that everyone complains about their database and the HN crowd uses a lot of MongoDB. There's certainly more total MySql/MSSQL griping, whether or not gripers/users is higher for MongoDB isn't really obvious.
I want to like Mongo, I'm all about "cutting my teeth on the bleeding edge", but I don't know what to think about MongoDB. Most conversations about it seem to go like this:
Lover: MongoDB is so much faster and easier than old school SQL!
Hater: It's fast and easy because it doesn't check if it's written data correctly, which leads to corrupt data.
Lover: Well you could always turn on the write lock.
Hater: If you turn on the write lock, it becomes slower than normal SQL databases.
Lover: Well you're just trying to use it the same way you use SQL. MongoDB is great for some problems and not so great for other problems.
Hater: What problems is MongoDB better at solving?
And then that's the end. I've never heard a convincing use case for this thing. If you can change that for me and give me one, I'd be delighted to listen.
> Lately I haven't read any news about a company migrating to Mongo, but rather most were either departing from mongo
They had some strange defaults to start with (to give them serious advantage in small silly benchmarks) like un-acknowledged writes. Yes you read that correctly, for years their default configuration was to throw write requests over the fence and assume they succeeded.
There are some horror stories of people's databases becoming silently corrupted. Those corrupted databases were then backed up and back ups were corrupted.
Eventually they had fixed their defaults but their reputation as an engineering company went down the hill ( I speak for myself here mostly).
From my experience a lot of people using MongoDB don't know what they are using. To them 'unacknowledged writes' and 'database level locks' sounds like Latin. They see short examples, cool mugs, other cool kids talking about how easy MongoDB is and they start using it.