[Neo] Dispell the myth? FlockDB vs. Neo4j

[Peter Neubauer]

Mmh,
FlockDB seems to be focused on making the graph very flat (just
user->followers) in order to be able to partition it. In that respect,
it almost implements a document model. I think the most interesting to
start with would be to implement it under Gremlin and run some algos
on in in order to test. Emil will write up more on FlockDB, but I
imagine the characteristics are more these of a Document DB than of a
Graph DB.

We will need to get a better grip on it before jumping to conclusions though.

Cheers,

/peter neubauer

COO and Sales, Neo Technology

GTalk:      neubauer.peter
Skype       peter.neubauer
Phone       +46 704 106975
LinkedIn   http://www.linkedin.com/in/neubauer
Twitter      http://twitter.com/peterneubauer

http://www.neo4j.org               - Your high performance graph database.
http://nosqleu.org                    - The biggest NOSQL event. Ever.
http://www.thoughtmade.com - Scandinavias coolest Bring-a-Thing party.



On Tue, Apr 13, 2010 at 1:11 PM, Jeremy Day <jeremy.day at gmail.com> wrote:
> All,
>
> I haven't looked at FlockDB at all, but would it be possible to perhaps
> implement the Neo API on top of it?
>
> Jeremy
>
> On Tue, Apr 13, 2010 at 5:26 AM, Laurent Laborde <kerdezixe at gmail.com>wrote:
>
>> I just heavily twitted about it :)
>> I'd call FlockDB a Key/Value/Relationship Store (KVRstore), but not a
>> graphdb :)
>>
>> --
>> Laurent "ker2x" Laborde
>> Sysadmin & DBA at http://www.over-blog.com/
>> _______________________________________________
>> Neo mailing list
>> User at lists.neo4j.org
>> https://lists.neo4j.org/mailman/listinfo/user
>>
> _______________________________________________
> Neo mailing list
> User at lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
>