Blank page with "Error establishing database connection."
Is that why you should never use MongoDB? :-)
Why you should never use MongoDB (2013)
11–20 of 188 posts
Re: Why you should never use MongoDB (2013)
#12Is it a joke? > Error establishing a database connection Or is it truly an error? In a page that from the title is bashing another DB
Amusingly ironic, eh? ;)
Re: Why you should never use MongoDB (2013)
#13This 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.
before: mongodb is bad because it imposes we handle the case where we'd like to shard the db (which breaks joins).
after: mysql is sooo much easier with joins. Who cares about sharding anyway.
I hope people understand distributed systems a bit better today, but I don't have high hopes.
Re: Why you should never use MongoDB (2013)
#14> Error establishing a database connection
Why you should never use database
Re: Why you should never use MongoDB (2013)
#15Your "I'm better at it than you are" is childish. I can't take you seriously after you post something like this.
Furthermore, again, as stated in the previous discussion, using something badly and not learning the ropes, but then claiming such an awful title is joke-worthy.
"Why you should never use MongoDB" - You mean "Why you should never use MongoDB if you aren't capable of learning how to use it correctly". Infact, just because it doesn't fit your instance doesn't mean it doesn't fit another persons instance.
Awful article.
Re: Why you should never use MongoDB (2013)
#16I think it's ironic that the page says "Error establishing a database connection".
As someone who used MongoDB extensively in the past (8TB+ of data) and also managed the devops side of things, I can tell you straight out that MongoDB has a place in a lot of startup stacks.
I would likely not use it as a main source of truth for any application. However for a lot of things, it's a good database.
Since I can't read the post I can't really address the points made in it, so at this point enough said.
Re: Why you should never use MongoDB (2013)
#17Is it a joke? > Error establishing a database connection Or is it truly an error? In a page that from the title is bashing another DB
It's truly an error. This blog post was written in 2013.
Re: Why you should never use MongoDB (2013)
#18"Error establishing a database connection" The irony is thick.
Re: Why you should never use MongoDB (2013)
#19The post should probably be titled "Why you should not pick a technology based on hype and without evaluating it first". While MongoDB has (and probably still has) some flaws and is not the perfect DB system, there are valid use cases where it can be a good choice. Building a social networking site that requires rich queries along a relationship graph is most definitely not one of them.
Re: Why you should never use MongoDB (2013)
#20Ironic: http://i.imgur.com/RGApTVz.png
