Why you should never use MongoDB (2013)

...but this is not a reason to stop using a RDBMS, just a reason to use it in the right places and for the right things. Using it to retrieve objects to fulfill every request is not the proper way. There are caching solutions which shine at performing this task.

...just as there are applications for which a variety of key-value stores shine.

Re: Why you should never use MongoDB (2013)

#5

Post by zippoxer » Mon, Aug 15, 2016, 2:55 PM UTC

I stopped reading where it said "never".

Re: Why you should never use MongoDB (2013)

#6

Post by hobs » Mon, Aug 15, 2016, 2:56 PM UTC

SmellTheGlove wrote: post #3

This is from 2013 - honest question from someone that doesn't know, is it still relevant?

If you read the post, the problem wasn't Mongo as much as they chose the new hotness (document db/graph model) when in reality their problem was already well solved by a RDBMS and tabular model, they had classic problems like duplicate data and performance issues when they tried to use a document db as a RDBMS.

They changed over and everything was fine.

Re: Why you should never use MongoDB (2013)

#7

Post by weddpros » Mon, Aug 15, 2016, 2:56 PM UTC

aka. The Mongodb hater's bible

EDIT: guys, be honest... if this article appears again on HN today, it's because mongodb haters are still alive and well. Downvoting my comment doesn't make the arguments in this article more valid. At least my comment downplays the importance of this article which is on HN's first page, which makes it relevant.