News for hackers. Stuff that matters.
Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by labria on Monday April 12, 2010 @05:27AM (#1258754)
I didn't look too deep into the "distributed" features (no docs yet, the code suggests sharding), but the feature set looks a lot like Redis sets.
Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by qhoxie on Monday April 12, 2010 @05:43AM (#1258768)
Many (all?) of the distributed features (including the sharding) are part of gizzard, which it sits on top of.

http://github.com/twitter/gizzard

Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by labria on Monday April 12, 2010 @06:10AM (#1258813)
Makes even less sense to me, then.
Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by simonw on Monday April 12, 2010 @06:29AM (#1258835)
Redis is less than a year old. I doubt it was a serious contender when Twitter started building their own solution.
Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by emileifrem on Monday April 12, 2010 @07:46AM (#1258918)
Well, the data model seems very similar to Redis' from first glances [1], but FlockDB certainly seems to have completely different durability characteristics. So even if they started anew today they may end up building their own.

1] Which would make FlockDB less a graph db and more a key-value store with social network semantics for the values.

-EE [http://neo4j.org]

Re:FlockDB: Twitter's distributed, fault-tolerant graph data... by labria on Monday April 12, 2010 @07:52AM (#1258927)
Redis is a bit more than a year old. And it's been tagged 1.0 last september. I doubt that that the FlockDB project is much older than that.