On 10/15/07, Björn Granvik <[EMAIL PROTECTED]> wrote: > Hi Klas, > > ... > > ** Meta model > *"Organizing your Nodespace" and subreferences pattern. This looks like > a poor man's meta model. I've lobbied for a proper meta model support in > Neo since there are many things one could do with a such a concept. > This example could drive for home-grown solution where a standard > support in Neo itself would to the trick for me. > The pattern in itself looks fine, apart from scaling, I guess. A couple > of millions of customers might not be too fun. Does anyone have > experience with scaling this pattern? >
Yes. Use a linked list structure, from the "subreference node" have a NEXT_CUSTOMER relationship instead of a lot of CUSTOMER relationships to the customers. Or use a tree structure (each "tree node" is allowed to have 100k entries and so on). List structure works good when you only need to insert,delete and iterate over entries. Tree is better when you need to go from an entry to the "subreference node" (for example to find the type). Also note that Neo API only use Iterable/iterators (no arrays) for collections and I have on my todo list to make it that way all the way down to the native store. -- Johan _______________________________________________ Neo mailing list [email protected] http://lists.neo4j.org/mailman/listinfo/user
