Neo4j: A Developer’s Perspective
From the post:
In the age of NoSQL databases, where a new database seems to pop up every week, it is not surprising that even a larger number of articles related to them are written everyday. So when I started writing this blog on Neo4j, instead of describing how freaking awesome it is, I aimed to address the most common issues that a “regular” developer faces. By regular, I mean that, a developer, who is familiar with databases in general and knows the basics for Neo4j, but is a novice when it comes to actually using it.
A brief overview for those not familiar with Neo4j. Neo4j is a graph database. A graph database uses the concept of graph theory to store data. Graph Theory is the study of graphs, which are structures containing vertices and edges or in other words nodes and relationships. So, in a graph database, data is modeled in terms of nodes and relationships. Neo4j, at a first glance seems pretty much similar to any other graph database model that we encountered before. It has nodes, it has relationships, they are interconnected to form a complex graph and you traverse the graph in a specific pattern to get desired results.
I don’t think you will see anything new here but it is a useful post if you are unfamiliar with Neo4j.
I mention it primarily because of a comment objecting to the AGPL licensing of Neo4j.
Err, if I am writing a web application to sell to a client, why would I object to paying for a commercial license for Neo4j?
Or is there some subtlety to profiting off of free software that I am missing?
I first saw this at: DZone.