Hacker News Reader

> Architecture is doing the right thing when growth can be handled by adding more of the same stuff. You want to be able to scale by throwing money at a problem which means throwing more boxes at a problem as you need them. If your architecture can do that, then you’re golden.

Source: http://highscalability.com/blog/2013/4/15/scaling-pinterest-...

View on HN

But that's not the first port of call. For instance, I've worked with a few companies that were perplexed why their site was going slow when they had invested heavily in great servers. It turns out the code was terrible.

I agree and I've seen that; however, the point of the article is that ideally you have rock-solid code and the only sane way to scale is just to add more of the same resources as the codebase is already optimized.

The reason I posted the quote was to answer your on your remark that it isn't a solution - it is close to an ideal solution actually, but not applicable everywhere and at any time (e.g. sloppy/non-optimized code as you pointed out).

Hope this makes sense.

Reply on news.ycombinator.com