Orientdb as a document-graph database

Question

I am using Neo4j and trying to find out the advantages of Orient as document-graph db over Neo4j.

How does it work in Orientdb to have features of a document database in a graphbdb? is the database in both mode (graph and document) using the same datasource? if so, then is it possible to edit data in documentdb and show it as a graphdb?

I worked with Orientdb and it seems that you can have your database either as graphdb or as documentdb, so I don't get the point of having both databases features in one db. I mean you can choose to have a pure documentdb or pure graphdb, but can't be some mixture of both, so it can be a graphdb like Neo4j or a documentdb like Mongodb. I need to know if I'm right or not?

Answer 1

Every time you work with OrientDB Graph API, you can always accessing to the underlying Document Database API, so you can mix usage of both. For example you can embed a document inside a Vertex...

Answer 2

The difference between document and graph is just a matter of modelling relation ships. Here you can see a detailed presentation. In short: if you use the document model you have direct relations between documents (vertexes), This means you can not store properties on the edge. If you use the graph model your relationships between documents (vertex) are going over a third edge-document where you store your edge-properties on. For me the big benefit of OrientDB is its ability to model documents using inheritance (for vertex and edges as well).