How to choose which type of NoSQL to use [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.

Closed 9 years ago.

Improve this question

There is a great list of various NoSQL database platforms at http://nosql-database.org. It categorizes each as a "wide column store", "document store", "key-value store", or "graph store". What I'm not finding is guidance on how to choose which of those 3 categories is most appropriate for a given problem.

What are the pros/cons or strengths/weakness开发者_如何转开发es of each type?

Which classes of problems is each type best suited for?

To be clear, I'm asking about distinctions between these 3 types of NoSQL systems and not specific implementations of them.

---

There is a good article (though it doesn't go in depth) on this exact issue on the thoughtworks site.

And this visual guide is excellent as well

---

After searching around a bunch more, I found that the documentation for RavenDB (a document DB) has a very detailed (and seemingly unbiased) comparison of each of these options, how they work, and where they are most appropriate. For anyone else interested, read Chapter 1 of this document: https://s3.amazonaws.com/daily-builds/RavenDBMythology-11.pdf

---

I've asked similar questions (but no real duplicates):

• When to replace RDBMS/ORM with NoSQL/DocumentStore
• When to replace RDBMS/ORM with NoSQL