ALL COVERED TOPICS

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

NAVIGATE MAIN CATEGORIES

Close

A NoSQL Community Effort

I learned that bloggers are usually writing a celebrating post once they are reaching different milestones in the lifetime of their projects. They do tend to remind their accomplishements and share the bright plans for the future. As you probably already guessed, it is indeed a special moment for this NoSQL blog, as I’ve just published the 1000th post. But instead of sharing with you stats and graphics, or other such achievements, I thought I should use this opportunity to tell you about what I’ve failed to do. And what I hope to be able to accomplish together.

A NoSQL Reference

Over time I’ve shared with you that I don’t believe in things like “learning programming in 24 hours” or “definitive guides to turning the world upside down in 5 simple steps”. But, I do believe that having a “good enough” NoSQL reference would help not only NoSQL newbies, but everyone in the NoSQL community.

So, my kind request to you is to help me fill in the gaps on this NoSQL reference page. What I’d like to have for all products listed in there (and for those that I’ve missed) is a short, structured intro, covering the following points:

  • project tagline: a short one-liner description of the project
  • data model (k/v, document, column, graph, xml, object, etc.)
  • distribution model (single server, master/slave, p2p replication, masterless cluster, etc.)
  • persistence model (disk, memory, memory with snapshoting, etc.)
  • client/network protocol(s)
  • elasticity
  • license
  • implementation language/supported OS
  • any other exciting features

While having this sort of NoSQL reference will be helpful, I think we should also have a….

Powered by NoSQL

The aim of the powered by NoSQL page is to provide as many references as possible to NoSQL case studies (successful or not!). It is essential for NoSQL adoption to start understanding the scenarios where NoSQL fits well and where it doesn’t. And what other better way to have this sort of knowledge than learning from what others have already done. But please do remember that this NoSQL case study reference is not supposed to be just a list of customers, so links to case studies are required[1].

That’s what I’ve failed to accomplish alone. But I’m sure that together, as the NoSQL community getting these done will be much easier. And I’d like to thank you all in advance for helping me achieve these goals. Thank you NoSQL people!


  1. We will continue to list customers, but just as a way to “nag” them to share their case studies.  ()

Original title and link: A NoSQL Community Effort (NoSQL databases © myNoSQL)