Great news for Neo. Most of the comments I see about neo4j are along the lines of "great technology, but doesn't quite cut it from a performance perspective".
I've seen some of the same comments, but I tend to take them with a grain of salt...in part because none of the commenters seem to have asked Neo or the community for help/advice when they've experienced performance issues. (The fact that the Neo demos I've seen have been pretty decent performance-wise leads me to believe at least some of the performance issues could have been solved if the people trying Neo out would have simply asked for help. It's usually difficult to wring the best performance out of a database of any kind without some hard-earned experience. The fact that many of the experimenters probably have little graphDB experience in general couldn't have helped the situation any.)
Definitely true. There are of course patterns that can slow certain graph traversals down, like having millions of relationships on one single node. Otherwise Neo4j handles up to a couple of billions of nodes/relationships/primitives out of the box, which is a good starting point for most of the cases.
Definitely agreed. Some of the comments I've seen from the neo4j author definitely lend to the fact that for most cases, the performance of neo4j itself won't be a problem at all.
