Dear Graphistas, if you have experience with that topic, could you please answer him. I think, real world answers help more than my general ones.
Thanks a lot Michael http://stackoverflow.com/questions/8332647/is-it-possible-to-use-graph-database-as-a-document-oriented-database Suppose I have a large ammount of heterogeneous JSON documents (i.e. named key-value mappings) and a hierarchy of classes (i.e. named sets) that these documents are attached to. I need to set up a data structure that will allow: • CRUD operations on JSON documents. • Retrieving JSON documents by ID really quickly. • Retrieving all JSON documents that are attached to a certain class really quickly. • Editing class hierarchy: adding/deleting classes, rearranging them. I've initially came up with the idea of storing JSON documents in a document-oriented database (like CouchDB or MongoDB) and storing class hierarchy in a graph database (like Neo4j). 1, 2 and 4 are then figured out naturally, and 3 solved by maintaining list of attached document IDs for every class in the graph. But then I figured that a graph database could actually do the document-oriented part of retrieving JSON documents by ID. At a first glance this seems true, but I'm still concerned about 2 and 3. Is there a graph database that is able to retrieve documents (nodes) at a speed document-oriented db's serve documents? How fast will it serve 3-like queries? I've heard a little bit about graph databases being slow, reification problem, etc. Is there a graph database that is also as comfortable for casual retrieving objects by ID, as CouchDB, for example? What is the difference between using document-oriented and graph database for storing, retrieving and editing JSON-like objects? _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
