nawroth

6 ms·

1. 1.▲
   by nawroth 16y ago

   Doesn't need to be a strict child when using a graph (not to confuse with hierarchical) database. Not sure what you mean by dangling edges, at least the Neo4j graphdb guarantees that edges are always connected at both ends. It's also ACID
2. 2.▲
   Neo4j development news(blog.neo4j.org)

   7 points by nawroth 16y ago|0 comments
3. 3.▲
   Mashups with the Facebook Graph API and Neo4j(blog.neo4j.org)

   19 points by nawroth 16y ago|1 comments
4. 4.▲
   The Neo4j REST Server - Part1: Get it going(blog.neo4j.org)

   22 points by nawroth 16y ago|7 comments
5. 5.▲
   Cool spatial algos with Neo4j: Part 1 - Routing with A* in Ruby(blogs.neotechnology.com)

   6 points by nawroth 16y ago|2 comments
6. 6.▲
   by nawroth 16y ago

   You bet! The projects are just starting to collaborate, see: http://wiki.neo4j.org/content/Google_Summer_of_Code_for_Neo4...
7. 7.▲
   Modeling categories in a graph database(blog.neo4j.org)

   22 points by nawroth 17y ago|0 comments
8. 8.▲
   Access control lists the graph database way(blog.neo4j.org)

   4 points by nawroth 17y ago|0 comments
9. 9.▲
   Neo4j Graph Database 1.0 released(news.neo4j.org)

   43 points by nawroth 17y ago|14 comments
10. 10.▲
    by nawroth 17y ago

    To answer your question I think things will settle down -- in the long run it's too hard for developers to deal with all the alternatives and their differences. To get a high-level overview of the NOSQL space you could read this blog entry: