+Terrence Miao, if you want a good overview of the different types of NoSQL stores, read Fowler's NOSQL Distilled. It will give you a good understanding of the advantages and disadvantages of each style of store. Neo4J is a graph database which is very good for modelling relationships amongst entities. We used at Reece in a Hackathon to create product recommendations. Apologies for hi-jacking the question.
We use Neo4J because it is a graph database and graph databases are good where relationships between things are important and may need to be queried in both directions. For example an SQL database would be good at answering what orders a particular customer has but if you wanted to find out which customers bought a particular item or combination of items it would struggle.
Neo4j is pretty quick at traversing nodes in a graph but we currently use it on a single node and I am not sure about its clustering capabilities.
For more general pros and cons consult google but if you have any more specific questions let me know.
Folks, your first hand experience, plus pointing me to the right direction, are more valuable than I tread a own path in internet jungle, or try to find out a piece of meat in an enormous dog turd.
Neo4J is a graph database which is very good for modelling relationships amongst entities. We used at Reece in a Hackathon to create product recommendations. Apologies for hi-jacking the question.
You didn't mention you have contact with Neo4J before ...
Neo4j is pretty quick at traversing nodes in a graph but we currently use it on a single node and I am not sure about its clustering capabilities.
For more general pros and cons consult google but if you have any more specific questions let me know.
BTW, put your next lunch meet-up bill on me!