NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter



Graph Databases: What Are They and Where do They Fit

InfoQ’s Jonathan Allen talking to Daniel Kirstenpfad, founder and CTO of sones GmbH, creators of sones GraphDB:

Jonathan Allen: Can you explain what a graph databases is and why developers would choose one over a tradition database?

Daniel Kirstenpfad: […] o unlike other database approaches which only implicitly can form a graph structure a graph database explicitly represents a graph. And while other databases need to use indices and relational helpers (like relational tables which are coupled using JOINs) a graph database can traverse from one object to the next objects because those objects are organized to have index free adjacency.

While experimenting with another graph database, neo4j, I’ve found the lack of implicit direct node referenceability quite awkward.

Original title and link: Graph Databases: What Are They and Where do They Fit (NoSQL databases © myNoSQL)