Hi Demai,

I think it goes all of the way back on when graph theory started.

Maybe one of these links will give you the answer that you are seeking.

https://en.wikipedia.org/wiki/Graph_theory

https://en.wikipedia.org/wiki/Vertex_(graph_theory)

I am not sure about Noe4j.  I played with it couple of years ago (when Hadoop was being looked at to being supported).  The problem that I ran into was scalability.  That's why I made the switch to GraphX (Apache Spark) and looking back into JanusGraph.

I hope this help.

Thank You,

Irving Duran

On Thu, Feb 9, 2017 at 3:54 PM, Demai Ni <nid...@...> wrote:

Irving, 

thanks. I just watched the whole presentation. It is pretty helpful to understand tinkerPop. However it doesn't mentioned the storage design about why vertex, edges, and properties should be put together. On another note, does Neo4j keep the three in separated file?

Anyway, appreciate the pointer

On Thu, Feb 9, 2017 at 12:58 PM, Irving Duran <irvin...@...> wrote:

This is a good video that I would recommend -> https://youtu.be/tLR-I53Gl9g

I would keep your vertex, edges, and properties together.

Thank You,

Irving Duran

On Thu, Feb 9, 2017 at 12:49 PM, Demai <nid...@...> wrote:

hi, Guys

new to this form and looking for a few pointers.

I am fairly familiar with HBase, hence plan to use it as the backend. I went through the 'getting-started' tutorial, and have the example up and run. I am looking for a few pointers about the design(of familycolumn, key), and how/why it was designed in such way. And then like to lead to my next questions, is it flexible(and reasonable, beneficial) to store vertex, edge and properties separately?  To do so, which code should I pay attention to? 

Many thanks

Demai

--
You received this message because you are subscribed to the Google Groups "JanusGraph developer list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.