One con for me is the you can't shard Neo4j. That means that you have your whole dataset in ONE server.
So you have to scale vertically each time you want to have more data capacity.
-- Alan Robertson <al...@unix.sh> - @OSSAlanR "Openness is the foundation and preservative of friendship... Let me claim from you at all times your undisguised opinions." - William Wilberforce
That you can’t shard your Neo4j is a general statement.
I would argue that it is very difficult to shard a densely connected graph. There are many graph data sets however that are not densely connected that could be sharded (at the application layer). It depends on your data set and the types of queries you are running.
Another point from this discussion is that a table inherently has relationships. Each field is related to each other field by the fact that they share a row. The only data I can think of that has no inherent relationships would be a simple unordered list of objects. (As soon as you order them, you have a data structure with inherent relationships between the objects.)
--
You received this message because you are subscribed to a topic in the Google Groups "Neo4j" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/neo4j/mts6H9Py-2I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to neo4j+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.