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 Database: All content tagged as NoSQL Database in NoSQL databases and polyglot persistence

Are databases in the cloud really all that different?

Dave Rosenberg (CNET):

What’s important to note is that using a database in a cloud-like manner requires system architects and developers recognize the principles associated with building a massively distributed data store.

Traditional SQL-based databases such as Oracle, Microsoft SQL Server, and IBM DB2 were designed to run on a single physical node/cluster in a single location, typically hooked to unified storage with full control over all software/hardware elements.

Running the databases in a virtualized environment with multiple nodes and very limited control imposes obstacles that are difficult to overcome. The wave of NoSQL databases seen recently is a reaction to these limitations.

Yet another way you can look at NoSQL databases.

Original title and link: Are databases in the cloud really all that different? (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)

NoSQL Is ... SQL at Scale

Cannot wonder what happened to Benjamin Black since it’s only a couple of weeks since “yelling”: “NoSQL took away the relational model and gave nothing back”. But it looks like he came up with the answer:

This is SQL at scale: radically simple schema, extremely narrow interface, asynchronous writes, and application-layer management of data distribution and query aggregation. These are also the properties of many non-relational databases. At this scale, most of the advantages of a relational database — ACID semantics and complex, ad-hoc queries — are traded for other advantages: operational simplicity, linear performance scaling, geographic distribution, and extreme fault tolerance.

And I’d say this is only from the perspective of scale. Others to consider: data (as in format, importance, etc.), operational costs.

Original title and link: NoSQL Is … SQL at Scale (NoSQL databases © myNoSQL)


Big Data and NoSQL March to the Enterprise

On GigaOm the other day NoSQL was gone already, now it is cool again:

We’ve come a long way in the maturity of new big data and NoSQL solutions, as well as in our understanding of when and where they fit. No doubt we have far to go, but the companies that can match these new approaches with clear and simple enterprise use cases are the ones likely to prosper.

I guess it is which way the wind blows today… (nb: there is no mention of enterprises using NoSQL databases in the article)

Original title and link: Big Data and NoSQL March to the Enterprise (NoSQL databases © myNoSQL)


Spring Framework Goes NoSQL with Spring Data

Spring frameworks feels like be all do all these days. On the other hand, having NoSQL databases integrated with Spring framework may actually represent an opportunity to penetrate the enterprise world.

The primary goal of the Spring Data project is to make it easier to build Spring-powered applications that use new data access technologies such as non-relational databases, map-reduce frameworks, and cloud based data services. A secondary goal is to provide additional support for relational database technologies such as Oracle RAC and convenience classes for Java generic based DAO classes.

The first NoSQL database mentioned to be part of Spring Data is the graph database Neo4j.

On VMWare side things are getting a bit complicated: VMWare owns Spring framework, which owns Grails which integrates with Redis which has been acquired by VMWare earlier this year. And don’t forget to add GemStone to the mix.[1]

  1. Could you say this backwards?  ()

Original title and link: Spring Framework Goes NoSQL with Spring Data (NoSQL databases © myNoSQL)


Speeding NoSQL Adoption

The panelists[1] from the NOSQL evening in Palo Alto[2] event shared their plans on speeding NoSQL adoption:

  • lower adoption barriers for NoSQL databases
  • make products more developer friendly, by supporting features that devs are used to (secondary indexes, durability, etc.)
  • support more platforms (e.g. mobile platforms)
  • growing the NoSQL databases ecosystem

In my post about NOSQL evening in Palo Alto, I’ve noted that simplicity has different meanings for different departments. I’ve also mentioned previously — when covering Cloudera latest round of funding — that investing in the ecosystem is probably the best solution for speeding up the adoption.

I’ve been thinking lately that even if we continue to hear about NoSQL failures, most of the NoSQL databases have already passed the technical validation phase. What is needed now is to get as many live installations and start hearing what real customers’ needs are. It is time to set aside the project initial technical goals and perform a reality check in the form of live deployments. There are many things that we will be learning from real-life stories and we might even hear some surprises.

  1. The panel included people from 10gen, Basho, CouchOne, Cloudant, Cloudera, InfiniteGraph, Membase, Riptano, GoGrid, Scality  ()
  2. Thoughts from NOSQL Evening in Palo Alto  ()

Original title and link: Speeding NoSQL Adoption (NoSQL databases © myNoSQL)

Thoughts from NoSQL Evening in Palo Alto

I should start by saying that I love new technology as long as it proves to be useful and that it works. For example I’ve been using LiveScribe to record the great NoSQL Evening in Palo Alto event organized by Tim Anglade with InfiniteGraph support, just to discover later that it decided to lose everything. So, instead of being able to quote things from the event, I’ll have to rely on my memory, which is really really bad.

After Berlin Buzzwords, this was the largest NoSQL event I’ve participated to. With InifiniteGraph’s people support, Tim Anglade did a great job in organizing this event and gathered together in a panel quite a few leaders of the NoSQL market. Unfortunately there were a few notable absences too; Redis, HBase, Project Voldemort, Neo4j, and RavenDB being the ones I’ve missed. Anyways, knowing how difficult is to put something like this together, this is understandable.

Before getting to what I’m remembering from the event, I have to tell you that I’ve been impressed with the fact that InfiniteGraph has not pushed for their product during the event. They have been great hosts and I had enjoyable discussions with many of their people, especially Darren Wood the lead architect.

Now it is time to test how bad my memory is. In case I got things wrong, please feel free to correct me.

What triggered so much activity in the persistence space?

  • cloud computing
  • failings do lead to innovation
  • the changing nature of the applications
  • old ideas reoccurring in customer work

Simplicity has different meanings for different people

NoSQL databases try to be:

  • developer friendly
  • ops friendly
  • user friendly

As a side note, it looks like there is still a myth out there related to NoSQL databases not needing DBAs. While the title doesn’t need to be the same, every NoSQL database will need someone…

What is the market size?

The relational database market size is estimated at $27bil. Noone wanted to go on record with their NoSQL databases market estimation. The only number I’ve heard mentioned that “70% usecases can fit NoSQL solutions” (Roger Bodamer, 10gen)

(New) Data models

The data model determines the access model. This discussion continued over the dinner, when people tried to answer the question how connected is SQL to the relational model.

I’ve also seem to remember some interesting remarks about indexes:

  • indexes are a different data model that enable different access models
  • indexes will be orders of magnitude larger than real data

RAM is the new disk

There are many products out there which believe in RAM being the new disk (i.e. VoltDB, elastic caching solutions, etc.). Darren Wood (InfiniteGraph) mentioned that “graph analytics is a counter-example of using RAM storage for all data”.


Many NoSQL databases have chosen to use some form or another of open source licensing models. The reasons for doing it:

  • ease market penetration
  • there’ll always be companies willing to pay for software, support, streams of patches, etc.
  • open source gives great hiring resources

Some other disparate notes:

  • Many of the solutions are old, but the wrapping/packaging is new. For example, MarkLogic is a good proof document databases work, even if it is not one of the “cool” products.
  • Not all NoSQL databases are about size
  • OLTP is for knowledge classification; OLAP is for knowledge discovery
  • Will we have multi-purpose NoSQL databases?
  • Cold data should be on disk
  • Using the right protocol can help you skip supporting specific features. CouchDB is HTTP friendly, so it doesn’t need to directly have a caching layer
  • Are key-value stores offering too little compared to file systems?
  • SQLite has a great distribution model: it is basically everywhere.

For more accurate coverage of the event you can read:

Update: now we’ve got also the video!

Original title and link: Thoughts from NoSQL Evening in Palo Alto (NoSQL databases © myNoSQL)

NoSQL Database Architectures & Hypertable

In the series of NoSQL videos for the weekend, today we have Doug Judd’s presentation from October’s HackerDojo on NoSQL database architecture and Hypertable.

Original title and link: NoSQL Database Architectures & Hypertable (NoSQL databases © myNoSQL)

NoSQL Databases Weekly Review 33

This last week is pretty simple to summarize: the CAP theorem with flavors of CAP is wrong, CAP doesn’t apply, CAP explained, etc.:

There were definitely more interesting posts, but they got less attention than this whole CAP theorem revisited. My favorites:

Below is the complete list of articles:

Original title and link: NoSQL Databases Weekly Review 33 (NoSQL databases © myNoSQL)

Will Scalable Data Stores Make NoSQL a Non-Starter?

Once we’re no longer talking about serving data, but rather just about storing large volumes of it, NoSQL can seem nearly obsolete. For organizations willing to pay for data warehousing and analysis tools, the options are limitless: massively parallel software, data warehouse appliances, distributed file systems, and the list goes on. Pick your poison. Have lots of unstructured data to analyze and don’t want to pay for software? Try Hadoop. Plus, it might very well work with your existing data management software.

Now this is completely confusing… so I’ll not spend time trying to understand it.

But this other question sounds like a good one:

Will a scalable SQL option always win out against a NoSQL option? Even for unstructured data?

Just omit the reference to scalable and think about: 1) know-how and 2) tooling support. NoSQL databases do have a long way to go to become an equal option for everyone and every project (nb that’s not to say that NoSQL will actually fit all problems) .

Original title and link for this post: Will Scalable Data Stores Make NoSQL a Non-Starter? (published on the NoSQL blog: myNoSQL)


NoSQL databases and the Cloud with Guy Harrison

Guy Harrison (QuestSoftware, working on Toad for Cloud) interviewed about NoSQL databases and cloud computing:

I think anyone who’s been in the industry for a while, especially from an enterprise point of view, will understand that the data isn’t in the database just for the sake of the application. It’s not there just to be inserted, and updated, and deleted. It’s also there to be mined and analyzed and used for decision-making and trending. And the more data there is, the more granular data I’ve got, the more fine-grained decision making I can have.

Most of the of the NoSQL databases offer no solutions for that whatsoever.

There are many smart things said in the interview so make sure you read it all.

Couple of my notes:

  • what is big data?

“It’s the whole argument that it’s easier to leave the data where it is, on commodity hardware and then have an engine that can churn through it with brute force, rather than pay the costs of bringing it in to some structure and locking it down before you can use it.”

  • cloud computing and big data:

First, all of the cloud platforms have to provide some sort of elastic storage model otherwise their economic model is jeopardized.


If you’re in the cloud, you’re probably motivated more than usual to try NoSQL solutions; you probably want to scale up and down and pay for your resources that way, and relational databases don’t help there.


The problem, of course, is how the data is getting to the cloud. If you’ve got terabytes or petabytes of data, getting into the cloud costs money and takes time. Amazon’s solution of “you send us a hard drive and we’ll mount it” is a bit clunky.

Original title and link: NoSQL databases and the Cloud with Guy Harrison (NoSQL databases © myNoSQL)


NoSQL Databases Weekly Review 32

Last week most read posts about NoSQL databases

As you could expect the top news this week where about MongoDB Auto-sharding and Foursquare Downtime and then Foursquare MongoDB Outage Post Mortem. And I think there will be some more on this topic in the upcoming week.

  1. MapReduce and Hadoop Future: does Google Caffeine announcement make any difference to MapReduce and/or Hadoop future? A somehow related question is if Michael Stonebraker was right about MapReduce?
  2. Cassandra: Modeling A Facebook-Style Messenger: I said it before: from all NoSQL databases, the wide-column model is probably the most complex, so every examples and tutorial we can get they’ll prove useful.
  3. Why Enterprises Are Uninterested in NoSQL: two things are sure: 1/ Michael Stonebraker has a long history in the data space and 2/ his posts are generating lots of waves
  4. MongoDB: A ToDo App with Ruby and PHP: MongoDB practical language tutorials.
  5. Big Data from Sensor Networks: want some impressive numbers that we’ll have to deal with in the BigData era?

My favorites from last week in NoSQL databases

Original title and link: NoSQL Databases Weekly Review 32 (NoSQL databases © myNoSQL)