何时设计可扩展性？(When to design for scalability?)

 我即将开始一个项目，希望有一天能够扩展。 对我来说，关键问题是：我现在应该投入精力去设计这种可能性，还是应该在我到达那里时跨越那座桥梁？ 
 
 我知道这些事情是怎么回事：每个人都认为他们的项目可能会扩展，但大多数项目都没有。 
 
 是否有一套最佳实践可以让您在以后的阶段更容易扩展，而不会在可能永远不需要的东西上投入太多？ 
 
 显然，我没有可扩展网站的经验。 目前我倾向于Scala / Play！ / Akka。 从我从Akka网站上可以收集到的信息来看，它非常适合这种项目（因为它提供了一个工具集，允许在一台机器上进行开发并扩展到任意数量的机器）。 
 
 该项目是一个面向消费者的网站，涉及一些用户交互（评论，消息，投票等）。 但主要关注的是社论。 这不是Facebook :) 
 
 没有任何这些技术的经验（我的经验主要来自PHP，AS3，Objective-C），我现在可能有点太多了。 但是我不会马上去做。 我知道我需要使用Scala和Play获得一些经验！ 第一。 
 
 任何意见是极大的赞赏。 

I am about to start a project that I hope will some day require the capacity for scaling. The key question for me is: should I invest the effort to design for this eventuality now, or should I cross that bridge when I get there?
 
I know how these things go: everyone thinks their project might scale, but most projects never do.
 
Is there a set of best practices that will allow you to scale more easily at a later stage, while not investing too much in something that may never be needed?
 
Obviously I have no experience with scalable web sites. Currently I am leaning towards Scala / Play! / Akka. From what I can glean from the Akka website, it is very suitable for this kind of project (in that it provides a toolset that allows development on a single machine and scaling out to an arbitrary number of machines).
 
The project is a consumer-facing web site that involves some user interaction (comments, messages, voting etc.). The main focus is editorial, though. It's no Facebook :)
 
Not being experienced in any of these technologies (my experience mainly coming from PHP, AS3, Objective-C), I probably have a little too much on my plate right now. But then I am not going to go at it right away. I am aware that I need to get some experience using Scala and Play! first.
 
Any advice is greatly appreciated.

原文：https://stackoverflow.com/questions/9307883