How To Pick a Database? [closed]

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improv开发者_JS百科ed and possibly reopened, visit the help center for guidance. Closed 11 years ago.

In this day and age, with a new NoSQL databases popping up every weekend..

Are there any good and up-to-date resources on how to pick a database(s) that will suit your web application needs?

---

If you're interested in trade-offs and feature comparisons Wikipedia tends to be updated more than others.

Relational Database Comparison: http://en.wikipedia.org/wiki/Comparison_of_relational_database_management_systems

NoSQL Feature Comparison: http://en.wikipedia.org/wiki/Comparison_of_structured_storage_software

If you want a more direct answer you can always post the requirements you have and you'll get a lot of helpful answers. It's a pretty broad subject and, other than feature comparison matrices like the ones above, you'll mainly get subjective answers unless you have an objective question (ie specific requirements).

---

Cassandra vs MongoDB vs CouchDB vs Redis vs Riak vs HBase vs Membase vs Neo4j comparison

NoRAM DB => “If It Does Not Fit in RAM, I Will Quietly Die For You”

Although I would also advise considering a SQL data back end ( e.g. PostgreSQL, Drizzle ) with a cache layer, e.g. Redis on top of it. Unless you have an actual reason to use NoSQL. The reason can by the way be NoSQL is cool and I'd like to learn it, but if that is all, usually it may hurt at the end.

Does the problem have to do with money transactions? Are you going to have a distributed system?