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



Presentation: Graphs && Neo4j => teh awesome!

We’ve already seen some slides from Emil Eifrem’s presentation (@emileifrem) in our article The New Dimension of NoSQL Scalability: Complexity. But the video of his presentation is even better and you can check it yourself.

The presentation has 3 distinct parts:

4 trends for why NoSQL is happening right now

  • data set size growing exponentially
  • growing connectedness of data
  • semi-structure (data being more “unstructured”)

    => the impact on RDBMS performance

  • architecture

Next time I’ll be writing about NoSQL future, I’ll just make sure to remember these.

NoSQL Intro (from 10‘00” to 16‘00” and continuing after 46‘00”)

Probably the most condensed intro to NoSQL. There is also a fun part starting at 46‘00”. I bet you’ll like it!

Neo4J (from 16‘18” to 46‘00”)

My notes:

Every operation must be inside a transaction. We love transactions. We think that transactions are the fundament of databases.

This “statement” remembered me of Gavin King (Hibernate) a couple of year back. I do think that having atomic operations is essential and support for transactions is definitely nice to have. On the other hand I am not very sure how Neo4j will deal with scaling out — which is planned and worked on — and transactions.

Domain model and graph node interaction

This sounds (a bit) similar to JCR/Jackrabbit at the API level.

At implementation level it is rock solid (being in production for 6+ years 24/7). Not perfect at documentation level and ease of use.

Lack of documentation is an issue that can easily be taken care of. But Neo4j will have to look into improving the developers experience.

And now it is time to watch Emil’s Neo4j - the benefits of graph databases

Slides can be downloaded from ☞ here (PDF).