Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I fully agree here. A couple of years ago, when I went on interviews at startups, they were all using nosql db's and were proud of it. More recently, I've been interviewing at startups that are now bigger, need to mine the data that they've collected over the last few years, and now are migrating off of nosql db's to rdbms' (or creating strange amalgams of the 2). I did see this coming, but it was very hard to make them understand back when it was the coolest thing.


The reality is that developers are maturing in their understanding of different technologies and they are learning how to apply them in correct use cases.

There continues to remain a "golden hammer" syndrome where white horses and unicorns run free, but it doesn't exist.

Instead, the vision of "NoSQL" was to tell developers that they did not have to use relational data for everything, but could, instead, use the right tool at the right time. Why is this such a hard concept?

If you are a developer and you don't understand the tool you are wielding (it's pretty clear the author of this blog didn't), then you will incorrectly use the tool and experience pain.

That is the fault of the developer, not the tool.


Care to specify at which point the author of the blog post misunderstand MongoDB? Its not pretty clear to me about that.

Are you saying that one of the way he is using MongoDB is incorrect? If yes, what point did he say reflects that?

His rants seems quite specific.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: