[Neo] relational databases
peter.neubauer at jayway.se
Tue Jan 20 15:20:12 CET 2009
this is a great post!
Another interesting aspect of graph databases is IMHO thte absence of
any required relationships or attributes per se (of course enforcable
with higher level wrappers like the meta neo4j project). I feel it
gives a lot of flexibility to the data modeling and above all does not
require one to upfront define all possible future properties and
relationships, just to avoid major RDBMS updates later. This leads to
sparse tables and a lot of error and null handling code - not exactly
Of course there is a downside for this flexibility, the handling of
traversals in a more dynamic manner via Neo4j Traversers or SparQL or
other new query paradigms that can accomodate this kind of semi
Basically I can see all the arguments of RDF and the GiantGlobalGraph
apply to Neo4j and other data structures, but without the cumbersome
RDF-String based (lack of) programming model to do real world
Neo4j - the Giant Local Graph :)
Open Hearts, Open Minds, www.OpenCauses.org.
Phone +46 704 106975
http://www.neo4j.org - New Energy for Data - the Graph Database.
http://www.ops4j.org - New Energy for OSS Communities - Open
http://www.qi4j.org - New Energy for Java - Domain Driven Development.
On Tue, Jan 20, 2009 at 12:27 PM, Anders Nawroth
<anders at neotechnology.com> wrote:
> I've been thinking about how relationships are handled in different
> types of databases (and what problems that may give you), and one
> outcome of this is a blog post:
> I'd appreciate any comments on my blog on what I'm missing or whatever
> you have to add.
> Neo mailing list
> User at lists.neo4j.org
More information about the User