FlockDB: Twitter's distributed, fault-tolerant graph database

Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by nkallen on Monday April 12, 2010 @02:39AM (#1258567)

Note that it's in the process of being released: it's as yet unusable by outsiders. Honestly, I did not expect this to make Hacker News so soon. :(

I have not used Neo4J first hand. It has really cool features, but it is not a distributed database and has expensive memory usage. FlockDB is distributed, uses little memory, and has a very limited feature-set that is highly highly optimized for OLTP. It's not really an apples/apples comparison. Theoretically, Neo4J could be used as a back-end data-store in FlockDB.

[ Parent | on HN ]

Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by emileifrem on Monday April 12, 2010 @03:39AM (#1258624)

I agree that it's not apples/apples. From the first few minutes, I think the main strength of Neo4j is the rich ecosystem and functionality on top of it, and the fact that it stores an infinite-levels deep graph. In comparison FlockDB stores one level (e.g. user -> followers). The main strength of FlockDB seems to be that it has built-in distribution, which is something we're working on for Neo4j but it's not yet generally available.

All this of course based on just a quick glance, so I may come back all the wiser and revise my opinion later. :)

-EE [http://neo4j.org]

[ Parent | on HN ]