Bless them, that was nice of them; free advertising too.
On 14 Apr 2010, at 15:58, Laurent Laborde wrote:
> The FlockDB README changed :)
>
> old :
> -This is a distributed graph database. we use it to store social
> graphs (who follows whom, who blocks whom) and secondary indices at
> twitter.
Yup,
good statement that clearly marks what it is built for. GraphDBs FTW!
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/petern
The FlockDB README changed :)
old :
-This is a distributed graph database. we use it to store social
graphs (who follows whom, who blocks whom) and secondary indices at
twitter.
new :
This is a distributed graph database. we use it to store social graphs
(who follows whom, who blocks whom) and se
Hmm..
Yep, that sounds about right.
I wonder how long it would have taken to write a sharding abstraction for their
use case compared to writing FlockDB, but hey I'm not trying to second guess
the problems they have at hand.
I myself am pretty ruthless about what technologies I use, it just
> On that page they mention that FlockDb is built on top of Gizzard. I'm
> having trouble figuring out just what FlockDb really adds.
>
Briefly I *think* it does away with the (traditional SQL) need of one join
table per possible relation. E.g. in SQL you normally need one table to map
Object A to
>
> (not sure why they didn't use a proven high speed graph DB myself - but
> then I am biased!).
I am guessing its because they only need 1st order relations (there are
little friend of a friend or higher operations on twitter) and were very
worried about scalability and sharding (as far as I am
Hmm...it's trivial to implement just user->followers in a relational db
directly. Sounds like what they're mainly doing is just adding an easy
partitioning layer. But they just released partitioning as a separate
project, Gizzard:
http://engineering.twitter.com/2010/04/introducing-gizzard-framework
I think fair comments Peter. It would make sense to look at what distinguishes
Neo4J and of course (I'm sure you're doing this already) getting some serious
benchmarks running on Sun's test environment (or wherever) so that there are
easily comparable performance figures for the different uses o
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 t
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 wrote:
> I just heavily twitted about it :)
> I'd call FlockDB a Key/Value/Relationship Store (KVRstore), but not a
> graphdb
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@lists.neo4j.org
https://lists.neo4j.org/
Long time no post from me ;-) But it seemed worth commenting on.
I think it would be good to quickly leap to illustrate the differences and
twitter this ASAP before the morning twitter storm that will occur about this.
I find it hard to believe they're solution is going to perform anything like
Yeah, I choked on my coffee when I read FlockDB described as a 'graph db'.
Its a key / value store with the ability to create relationships between
keys.
I hope projects like this misusing the 'graph db' term will not tarnish the
reputation of 'proper' graph dbs!
Al
On 12 April 2010 22:06, Marko
Hi guys,
I saw this on Twitter:
"dviner @wbelk haven't looked at neo4j. seems hard to look at a non-distributed
graph db when a distributed graph db is also available."
Seems like people think "graphdb" means "graphdb" FlockDB is not traversal
ready (at least how I see it from their writi
14 matches
Mail list logo
