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



MongoDB and Eventbrite’s Social Graph

Brain Zambrano presented recently at ☞ MongoSV the way Eventbrite is using MongoDB for modeling their user/events social graph. Slides can be downloaded from ☞ here.

Now the slides are really interesting and provide a lot of details both about the setup and the implementation details. But if you check slides 19 to 22 you’ll see why I’m saying that graph databases should be used for any graph problem that involves more than 1-level navigation.

MongoDB Eventbrite Social GraphMongoDB Eventbrite Social GraphMongoDB Eventbrite Social Graph

Twitter has built their own ☞ simpler graph database, ☞ FlockDB, but as stated in the docs: “multi-hop queries (or graph-walking queries) are a non-goal”.

Original title and link: MongoDB and Eventbrite’s Social Graph (NoSQL databases © myNoSQL)