Applications that used to be desktops apps are now moving to the web, and these "cloud applications" are prime use-cases for NoSQL. Apps like Gmail, Google Docs, Dropbox are cases where a NoSQL might be a better fit than SQL, the same way Word.exe doesn't use SQL internally, instead it uses linked lists and hashmaps [1].
"In my experience this is what 99% of business support apps are doing."
Business apps are the original, killer use-case for SQL, and here NoSQL makes less sense, I agree.
[1] Some apps like Firefox started using SQLite for local storage, a technical decision I don't agree with.
I don't see anything in Gmail and Google Docs data usage needs that make NoSQL a better fit for them --only the need to scale with no sharing etc.
(OTOH Dropbox might fit the case, they only need some hierarchical store a la filesystem, with versioning).
the same way Word.exe doesn't use SQL internally, instead it uses linked lists and hashmaps
Yes, but Word.exe internally deals with just ONE document and it's data structures, does not manage metadata for many documents and does not have to provide aggregated info on them. That would be Windows Explorer, that manages many .docs. And that one, MS did have a plan to make more SQL-like.
Somewhere I worked before we used to import 100,000s of a companies email into the project system to display them against the system. They were all in an Emails table which just stored the body, I think there was an email header table and an email contacts table which was relationally linked directly to the Person table.
Worked fantastically, used to run an IMAP server off those tables for outlook integration.
Per gmail account, you'd still dump all the mails into one gigantic emails table, either an SQL or a NoSQL one.
As for the totality of the gmail accounts, well, you'd use sharding, which is the same whether you use NoSQL or SQL.
You also want to cache the hell out of it, which is easier done in a NoSQL model (e.g. if the cache layer is integrated and hence uses the same API as the persistent stuff).
But a SQL DB can also use the same transparent API for the persistent stuff with their standard Query API. It wouldn't even need to parse the SQL statement, just hash it and compare it. And you could also use a layer that makes it transparent, such as an ORM.
Only it's not like that, because SQL is a well defined way of thinking at problems, not just a particular implementation of it.
So, NoSQL is like saying NonFunctional. Or NonImperative. Or NoRegister VMs, etc...
So I guess it works.
NoSQL refers to the databases that are proposed as alternatives in areas where programming culture had gotten used to thinking that the only solution was an ACID-compliant relational database. It means, "hey, this isn't the model you're used to, but give it a try anyway." You can't figure out the word without knowing the culture it emerged from.
And now I'm getting post-modern.
Props for a well written article with lots of nice graphs but I dont agree with much of its content.
A few examples:
"software applications are not so often interested in in-database aggregation"
In my experience this is what 99% of business support apps are doing. Doing this aggregation in procedural application code will only give you more code to maintain and more bugs.
"joins are often handled at design time as opposed to relational model where joins are handled at query execution time"
Im glad you know beforehand about your changing requirements over the next 10 years and can "design" your joins for every eventuality right now. It feels like the exact oppisite of agile.
I also agree with the very insightful comment by Voice in the wind (comment #4 below the article)