[ris]

No. No. Never do this.

You never actually know where your bottlenecks are going to be until they arrive and by designing everything with a "super scalable" architecture you will be making development ten times as painful and expensive as it needs to be while throwing away nice things that come "for free" and "just work" at the mid-low end like transactions.

Amazon and Netflix don't want to have to use their hideously complex and inefficient service architectures - they're forced to because of their scale.

Most people who engineer their systems for hyper-scale from the get-go never see a whiff of anything that looks remotely like high traffic. Often they go out of business before they get anywhere near that.

And once you get to serious scale, you really shouldn't still be running the code from back when you didn't really know what your business/product was.