Don’t let me giving away the punchline keep you from reading the whole thing:

If you have an implicit schema — meaning, if there are things you are expecting in that JSON — then MongoDB is the wrong choice. I suggest taking a look at PostgreSQL’s hstore (now apparently faster than MongoDB anyway), and learning how to make schema changes. They really aren’t that hard, even in large tables.

Sarah Mei » Why You Should Never Use MongoDB

Eugene Crosser November 21, 2013 01:24

Such an amusing and well written (and longish) post.

All to explain a problem that is glaringly obvious from the start…

Michael K Johnson November 21, 2013 06:07

If it were glaringly obvious to most people, the article wouldn’t have been written in the first place. ☺

Perhaps the problem is that “MongoDB” has the letters “DB” in immediate proximity and capitalized, misleading people into thinking that it is intended to be a database. Frankly, when I see “DB” in a name, I tend to assume that was at least the intent until I understand to the contrary.

David Megginson November 21, 2013 10:23

It’s basically the beginning of the end of the #NoSQL movement as such — it needs to start defining itself by what it is instead of what it isn’t.

Imported from Google+ — content and formatting may not be reliable