99% of database deployments are made by a guy like this and they are hell on earth (thousands of tables, 20+ recursive joins between them, a specification that spans more than 500 tables, "and that's just the 'inventory' database". But hey! the guy must know what he's doing! he's got 'the theory' and Oracle certifications here and there...
At the end or the day the best theory is the one that works. An experienced and honest DBA should propose the tools that better fit the problem given instead of trying to fit the problem within the toolset he arbitrarily prefers.
Disclaimer: I'm using 'he' in its generic gender-neutral form. It wouldn't be nice to get fired just for a quick and casual HN comment.
This isn't just about Oracle certifications. This is about databases that can actually handle the "hell on earth" complexity that some systems simply have. Or do you think you can run a bank or an insurance company on a key-value store, implementing their immensly complex business rules with a couple of hash tables?
Granted, every problem can be solved with the appropriate tool and some NoSQL tech is indeed appropriate for some problems. But then again, SQL is actually a pretty good tech for 90% of the problems.
To me, KVS and RDB are just two sides of the same coin. If you start modelling properties your DB will look like a RDB, if you start with objects first your DB will look like a KVS. I prefer KVSs because it's more natural for me to think of everything that way.
Here I'm abusing the scope of the word KVS, what I pretend to mean is some kind of "document" store accessible/sorted by keys.
To me, quite frankly, his article sounded more like a pro-LINQ marketing campaign than anything else :-). No wonder he's propagating duality between SQL and NoSQL (coSQL) when he planned on creating a company called Applied Duality Inc...
Nice one but yeah it kind of sucks that the theory is used like a preamble for trying to sell you LINQ
For instance:
"Is it based upon a rock-solid theory"
So a hash table lookup is not based in a rock-solid theory?
"Can it handle relational data models"
Is this an advantage if your data doesn't have relations? (i.e logs)
"Is it even a well-defined concept"
NoSQL is an umbrella term, replace it with Key-Value data store or with a Document store and you will see it is pretty well-defined.
And the list can be extended...
The mainly problem with NoSQL databases is that they are keep being used in places where a relational database would make more sense and after failure those people are very vocal about it. At the end of the day is a tool and you will be fine in using it as long as it is the right tool for your need.