Before Google came along and showed the business people the benefits of horizontal scaling, any software engineer would be automatically considered crazy if they suggested an architecture that wasn't built on a central RDBMS.
So you have to weigh it against the other cargo-cult. How many startups along the way have failed due the inability to scale horizontally?
How many have failed due to too much cost and complexity associated with re-engineering an architecture in which the assumption of fully ACID transactions permeates the entire codebase? (While the phone is ringing off the hook because production systems are falling over under load.)
Long story short, I have to grant that you shouldn't worry about scaling up too soon or too quickly. But that don't go to the opposite extreme by putting it off until the last possible moment.
D igital Unix
N etscape Commerce Server
B erkeley DB (NoSQL!)
C code (linked into the HTTP server)
I'd call BDB "pre-SQL" rather than "NoSQL".
1. Amazon/Facebook/Google have a lot of traffic.
2. Amazon/Facebook/Google use X to scale horizontally. ergo:
3. My little startup should use X and scale horizontally.
What they fail to realize is that most of these companies would be ecstatic if they could scale machines vertically, if they could focus on great user features instead of having to figure out how to shard in the application layer. You should never forget that Amazon, Facebook, and twitter all started out as pretty basic LAMP stacks and built the tools when it was obvious that no other tool would do. I think google's an exception because their MVP was in fact a web scale application. So by all means, vet your idea, get some customers, get traction, and scale the cheap way by buying more ram for as long as you possibly can.