Hi Ilya!
1) Inheritance.
Suppose I want to draw tree where every node is derived from other node; say
Car à Sedan à Toyota
So when creating Toyota node I don’t need to recreate same properties and
relationships that Sedan has.
I think this example can help you:
We are evaluating Neo4J for a business critical application. There will be a
User Interface UI component to browse the graph, create nodes and properties
as well as create/modify relationships. The data set spans across 7 domains
and expected to be around 40 GB.
User will manipulate data in 3
Max and Anders,
Thanks much for your replies and detail info!
I think I have better understanding now about reusability via inheritance
and interfaces. I see now that if I want to define things once and then
extend/reuse them I simply need to create my own wrappers in language of
choice
Ilya,
Remember that we have no 3 way relationships (as in types), you have use a
node for anything that connects more than two objects. So break down Show
into Episodes if you want to to track the 1st (or only) airing of that
episode.
Actor 1 = Node 1 Class Actor
Show 1 = Node 2 Class Show
We have stress tested neo4j with over 500 concurrent users in a webapp with
a smaller dataset and we found no performance issues.
We even wrap their api in a domain layer that adds some extra overhead.
One thing to keep in mind is that if your data ever grows to a point where
it needs to be
5 matches
Mail list logo
