{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Melony? 的问题《How to choose which type of NoSQL to use [closed]》','https://www.manongdao.com/q-1305962.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
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/weaknesses 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.
I've asked similar questions (but no real duplicates):
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