Thank you for your replies. I think I'm going to go with Neo4j for now. CouchDB looks really interesting though.
I just couldn't resist the true Ruby flavor of Neo4j.rb http://github.com/andreasronge/neo4j/tree/master Compared to the seductive sexiness of Ruby syntax, JavaScript is still something I like to avoid if possible...... just a personal preference. It seems like if the graph traversal problem could be "solved" in couchDB with a slick interface, it might be a compelling reason for some to join the CouchDB camp. David :) On Sat, Jul 4, 2009 at 8:45 AM, Chris Anderson<[email protected]> wrote: > On Fri, Jul 3, 2009 at 12:20 PM, David > Beckwith<[email protected]> wrote: >> Hi, >> >> I'm deciding between CouchDB and Neo4j for a project. What's really >> important to me is the speed of graph traversal and scalability. >> >> CouchDB wins in scalability I think, but probably Neo4j wins in graph >> traversal. > > CouchDB's map reduce views aren't really suited for graph traversal, > but external indexers are a first class citizen. Take a look at the > CouchDB Lucene project to see how you can integrate any incremental > indexer: > > http://github.com/rnewson/couchdb-lucene/tree/master > >> >> http://highscalability.com/neo4j-graph-database-kicks-buttox >> >> How well does CouchDB with graph traversal. And is there a way to map- >> reduce graph traversal? >> >> Thanks, >> David :) >> > > > > -- > Chris Anderson > http://jchrisa.net > http://couch.io >
