Everybody knows that relational databases don't scale because they use JOINs and write to disk.
Also, relational databases weren't built for web scale. MongoDB handles web scale. You turn it on and it scales right up.
And before you knock shards, shards are the secret ingredient in the web scale sauce. They just work.
Furthermore, relational databases have impetus mismatch, and Postgresql is slow as a dog. MongoDB will run circles around Postgresql because MongoDB is web scale.
Edit: Whoops, just read your reply :)
http://en.wikipedia.org/wiki/Poe's_law
"without a clear indication of the author's intent, it is difficult or impossible to tell the difference between an expression of sincere extremism and a parody of extremism"
I am a happy Postgres user and always default to it unless I am really sure a project calls for something else.
And same here, I tell people to start their datastore selection with looking for a reason NOT to use Postgres.
However, if you have any of the following: (1) vastly different security requirements for different parts of your datastore (2) vastly different backup schedules or temporal sensitivities (3) privacy requirements deriving from different legal jurisdictions (4) wish to scale by running on commodity hardware (5) cannot tolerate any downtime whatsoever ... and probably many other cases ... then in my experience you are going to meet some serious issues with conventional RDBMS, at least with the vast majority of configurations.
I'm all for logic and reason too... but your comments seem closer to name-calling and a single example.
Anyway, in a lot of environments it's application's that drive choice of database engine - not the other way round.
I can't think of anything that is magnificently easier or better at solving your numbers, especially all together. #4 seems less relevant, is it really cheaper than operationalizing a distributed system? These days, likely for situations where consistency can be relaxed. Not so for many business workloads.
Can you enlighten us with some example products for your numbers?
Consider an inventory system for a big box retailer. I can't think of anything better than a fat-ass RDBMS as the primary data store. Sharding sounds like a horrific idea. There are myriad workloads like this.
Personally, I've seen pgsql handle terabytes of data just fine and it wasn't really noteworthy or a source of problems to even bring up considering something else. YMMV but it's a good idea to use logic and reason to dictate architecture instead of following the shiny thing or hubris.