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



NoSQL: All content tagged as NoSQL in NoSQL databases and polyglot persistence

NoSQL and Django Panel Video

Featuring Jacob Burch, Alex Gaynor, Eric Florenzano, Jacob Kaplan-Moss, Michael Richardson, Noah Silas[1]:

You probably know already that Django and NoSQL is hot!

  1. Unfortunately it looks like the real people on the panel aren’t the same with the ones listed.  ()

Original title and link: NoSQL and Django Panel Video (NoSQL databases © myNoSQL)

SQL vs NoSQL: Twinkle, Twinkle, NoSQL!

Story and script by Latha Annur Subramaniam:

In case you have a hard time reading it:

RDBMS (SQL) was worried when the news about a new technology called NoSQL

SQL: Oh, he is this new NoSQL guy. People say he is here to beat me out. Hmm. I just hate him!

NoSQL: Howdy, senior SQL. How are you?

SQL: um… uh… oh Hi young man. Looks like you are new to this place?

NoSQL: Oh yeah! Just out of the ‘Latest computing trends’ school.

SQL: He is just a fresher. But I am his great grand senior. He can never take me down.

SQL: Hey, your name NoSQL sounds strange. Sounds like you are an anti-SQL guy.

NoSQL: Hm… true. I fell so unfortunate of my name. But I am never al alternate to you. In short, I am a new solution for the fresh new problems of this computing era… the “WEBSCALE” era.

SQL: (Hey he sounds modest. Am kinda like this guy) Oh. Am hearing this term for the first time. What is this W-E-B SCALE thing all about?

NoSQL: Interestingly, these days humans lead a much active social life on the WEB only.

NoSQLL Just like in their real life, people always need more and more of everything. Tweet, Search, Maps, Blog… their needs never end ;-)

SQL: Hmmm. Now I get it. I’ve been the darling for the enterprises for their data storage needs. But maybe they will abandom me and choose you, when they need more scale?!?!

NoSQL: Partially true. I can help them in scaling massively. But you are still the best in a lot of things.

NoSQL: For example, you are the Superstar when it comes to ‘transaction based apps’. I can never beat you in your ACID qualities

NoSQL: Also, I am still not the best for ‘Reporting’ requirements. While my ‘schemaless’ quality helps dynamically add different types of data, it causes the drawback of not being helpful for reporting.

SQL: I fell you are the right fit for the modern social apps.

NoSQL: You are the right bet for the critical business apps… soon until I catch up with you


SQL: Yup. I wish you good luck, young man.

NoSQL: Thank you, senior. Btw, my name doesn’t mean a NO to SQL!!! It is only that I am NOT only SQL :-)

SQL: and so I dedicate this song to you buddy:

Twinkle, twinkle NoSQL
Was wondering who you are
Out into this computing world,
I wish you success all around!!!

Definitely not as good as MongoDB is web scale.

Original title and link: SQL vs NoSQL: Twinkle, Twinkle, NoSQL! (NoSQL databases © myNoSQL)

Questions about Caching and Persistence

Something to think about it:

  • if you are using some caching in your application, would you call that the persistence layer?
  • if you are using a distributed cache, would you call that your persistence layer?
  • if you are using a replicated and distributed cache, would you call that your persistence?
  • if your replicated and distributed cache does some sort of snapshotting to disk, would you call that your persistence?

Some are saying ☞ RAM is the new disk, so I’m wondering what their answers to the above questions are.

Original title and link: Questions about Caching and Persistence (NoSQL databases © myNoSQL)

NoSQL, Tradeoffs, and Software Engineering

Steve Klabnik (@steveklabnik):

Software Engineering is the art of choosing the correct set of tradeoffs

True, even if not specific to NoSQL databases alone.

Original title and link: NoSQL, Tradeoffs, and Software Engineering (NoSQL databases © myNoSQL)

Redis: Thoughts and Counter-Thoughts

Kenn Ejima ☞ posted his thoughts about NoSQL, scalability and O(N) as a preamble to some details about Redis persistence, concluding:

For people who don’t really grok what’s been said in this post (maybe because it was just too long to read), my recommended setup is: “Use Redis for small datasets that don’t grow fast (stay far less than 1GB). Have at least 2x memory than the dataset. Use default snapshotting and disable AOF.”

Considering this time I was one of those that didn’t really follow the first part of the article, filing it under “not sure what all these have to do with Redis persistence implementation”, I’ve found Jeff Darcy’s ☞ follow up adding a bit more context(!) to the discussion:

I’d rephrase above as “Use Redis for small datasets (less than 50GB this year) that don’t need to be highly available, have memory at least 2x your actual dataset (until the snapshot implementation improves), use frequent snapshotting or AOF (depending on your need for performance vs. durability – not both) and always avoid overcommit.” I also have nothing against Redis, it’s a fine tool for what it does, but I think its durability story is a bit confused and its reinvented VM can only serve a need that it’s not good for anyway. As always, the real answer is to use multiple data stores to serve multiple needs, with careful consideration of the tradeoffs each represents.

Original title and link: Redis: Thoughts and Counter-Thoughts (NoSQL databases © myNoSQL)

Django Getting NoSQL Support in Trunk?

We’ve covered Django and NoSQL extensively over here and now the news it that “official” NoSQL support might get into Django trunk:

Waldemar Kornewald: in my last discussion on django-users Russell told me that he’d like to see four proof-of-concept (or better) backends before considering NoSQL for inclusion in trunk. The primary point was that enough eyeballs have looked at the API, first. Now we finally have four backends for Django-nonrel:

  • App Engine (used in production), developed by Thomas Wanschik and me
  • MongoDB (used in production), developed by Flavio Percoco Premoli, Alberto Paro, George Karpenkov, and me
  • Cassandra (alpha/experimental), developed by Rob Vaterlaus with very minor hints from me
  • ElasticSearch (alpha/experimental), developed by Alberto Paro

Neo4j integration with Django seems to be missing from the list.

Original title and link: Django Getting NoSQL Support in Trunk? (NoSQL databases © myNoSQL)


NoSQL Databases: The Missing White Paper

Great piece, getting most of the things right, published on Pythian:

NoSQL databases are a good solution for a specific set of problems. Before choosing NoSQL database make sure you understand the application you are writing and its requirements. Be sure that NoSQL model will work, that it provides value and that you can live with the trade-offs. Make sure you understand the specific NoSQL database that you chose and that it fits your requirements. Make sure you know how to model your data in a way that uses this database in the best way and that you can deploy it in operations without losing sleep. Do your own tests – don’t believe blog posts and benchmarks. Deployed correctly, NoSQL databases are an efficient and reliable solution for a set of non-relational applications. Chosen for the wrong problems or the wrong environment, they will make your life very difficult indeed.

Should replace the ☞ Wikipedia article.

Original title and link: NoSQL Databases: The Missing White Paper (NoSQL databases © myNoSQL)


Big Data: What is a BigData Architect?

A recent job announcement on the ☞ NoSQL Google Group stemmed a few hilarious reactions. But I think it would be interesting to answer the question of is there such a thing like a BigData architect? What would be the qualifications of a BigData architect?

Based on this job post (nb I’ve removed most of the buzzwords in the announcement), a BigData architect would have extensive experience dealing with data modeling and data management (both relational and non relational) and designing and operating distributed scalable systems.

Personally, I think BigData is just a relative term: what is big data for a startup will not represent big data for Facebook, Yahoo, or Google. Also, getting from 2 servers up to tens with a couple of people and scaling from tens to thousands with tons of engineering support and budget is just a different “scale”. So, I guess the question remains: what is a BigData architect?

Original title and link: Big Data: What is a BigData Architect? (NoSQL databases © myNoSQL)

NoSQL: Do You Need to Associate Your Product with it?

Mohammad Abdurraafay in a post about Apple Core Data:

My take on Core Data is, because it’s just not being Open Sourced, it’s not filed under NoSql. Otherwise, it’s the only NoSql on the best mobile platform, i.e. iOS and probably the first.


This seems to be a reoccurring theme for existing storage solutions and not only. And I bet things will get more intense in the near future.

Indeed there are various arguments that can be used to associate your product with NoSQL databases: the data model, the processing model, the lack of SQL, etc. You have a key-value store (e.g. BerkleyDB) it is NoSQL. You have an object database or its new reincarnation as graph database, then you have a NoSQL database. Your product deals with BigData, then it is NoSQL.

But the real question is: if your product is already filling a market need and is well positioned, why would you try to place it under a buzzword umbrella?

Original title and link: NoSQL: Do You Need to Associate Your Product with it? (NoSQL databases © myNoSQL)

NoSQL: 44% Business IT Pros Ask What's That

According to an InformationWeek survey:

Heck, 44% of survey respondents hadn’t even heard of NoSQL.

If you think of it, I’d say that percentage is even lower than the reality. Not to mention that except Hadoop, I don’t think there’s any NoSQL adoption in the enterprise world yet.

Original title and link: NoSQL: 44% Business IT Pros Ask What’s That (NoSQL databases © myNoSQL)


NoSQL CouchDB founder turns to phone and cloud services

Gavin Clarke (The Register):

NoSQL start-up CouchIO is targeting mobile and clouds after just a year of trying to monetize the company’s CouchDB document store.


Rather than to replace SQLite, Katz believes that CouchDB has a future by being used in addition to SQLite — primarily on document-centric apps such as email, calendaring, scheduling, contacts, CRM, time sheets, and inventory. “That’s where Couch really shines,” Katz said.

Back to origins?[1]

  1. Before creating CouchDB, Damien Katz has been working on Lotus Notes.  ()

Original title and link for this post: NoSQL CouchDB founder turns to phone and cloud services (published on the NoSQL blog: myNoSQL)


BigData: How Data Strategy Will Change

most every company is living in its own version of the Big Data era. Two forces define this era: size and speed. And those forces are driving companies to consider new choices for how they deal with data.

A good read about what drives BigData and where we are heading to. Ignore for a second the company and product names in the article and think where NoSQL databases, distributed filesystems, RDBMS will fit in.

Original title and link for this post: BigData: How Data Strategy Will Change (published on the NoSQL blog: myNoSQL)