I'm working with a game developer where NoSQL solutions have been chosen and for good reason--speed. Relational is a pretty big burden on the team when they can just develop and throw chunks into a bucket at ease without a DBA on hand.

On the article. I don't really see the light. I mean, how is having more control over your data and the pipes in which your data flows mentioned as somewhat of a negative thing? That's a good thing! Sure, it comes at a price, but the end result may be well worth the effort if you had covered it in more detail.

At the end of day, it should be obvious MapReduce would be a cultural shock to any SQL developer. It's not SQL! These things are pretty obvious because it's a completely different direction from their possible current skillset.

Like... Why are we considering SQL for NoSQL outside of trying to keep Johnny the SQL Developer employed? These are better questions to answer than trying to satisfy those who do not want to move away from SQL. For example, covering what the actual business or project benefits are to using one or the other? I already know Johnny is going to be on edge when we start moving away from SQL, but what can we benefit outside of him? The business or project SHOULD outlast Johnny and me regardless of his or my personal preference.

It's about the tools that get the job done for me. How is this tool with or without SQL going to help me?