Premature Scaling Debate

Scaling is likely to be the biggest problem, not app development.

Scalability problems are not just for the web :)

Don't needed? Even the book of Founders at Work is full of stories where the problem was scaling (delicious, paypal, blogger, ...). Every startup that's going to work well is going to have this kind of scalability problem (and it is most of the time related to DB and not HTTP front-end side).

IMHO until you hit scalability issue don't try to spend your time and money there yet

people learned how to scale, not a big deal unless you are handling 1/3rd of the internet traffic for a specific industry.

Similar to not worrying about scaling because 99% don't get to the point where they need scaling.

Forget about scaling, it does not matter.(Unless you're building something that needs to scale day 1, say, an aggregator, a search engine, or something like that.)

Without knowing what the cause of those scaling problems were (CPU, memory, IOPS, etc.), I’ll have to take your word for it. But having worked at several startups, I can say that it’s a common disease that engineers start to optimize for the “we’re going to have a jillion customers” case long before they even have one customer, and that adds a whole bunch of complexity, cost, and schedule to the development, which increases burn and stands between the company and its cash-flow positive date. In

"X doesn’t scale" is a myth.http://news.ycombinator.com/item?id=160730

Seems like an application of "do things that don't scale".https://paulgraham.com/ds.html