我应该在多大程度上担心缩放问题？
我计划从头开始一个新的 Web 应用程序，但我想知道我是否不太关注可扩展性。我应该从一开始就担心这个问题，还是最好先关注应用程序本身，然后稍后扩展 如果我真的成功了呢？
I am planning to start a new web application from scratch, but I wonder if I am not obsessing too much over scalability. Should I worry about this since the beginning or is it better to focus on the application itself first and scale later if I happen to be really successful?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
一般来说，出于多种原因，一开始就担心可扩展性还为时过早，而且会分散注意力。
当您遇到问题时解决问题。
过早担心可扩展性往往会耽误你做一些没有多少收获的事情。通常，直到在现实世界中使用某些东西时，您才能真正理解性能影响。
Generally speaking, its premature and distracting to worry about scalability to begin with for several reasons.
Solve a problem when you have a problem.
Worrying about scalability too early tends to delay you doing something for not much gain. Often you don't really understand the performance implications until something is used in the real world.
为自己定义一些目标，例如您希望应用程序一开始能够服务的每秒用户数。然后开发应用程序并执行负载测试以确保满足您的目标。如果是，您可以将其向公众发布，看看会发生什么。
Define yourself some goals such as for example the number of users per second you would like your application to be able to serve in the beginning. Then develop the application and perform load testing to make sure your goal is met. If it is, you could launch it to public and see what happens.
现在您应该关注应用程序的演示、功能和安全性。当您需要时，可扩展性就会出现——但请帮自己一个忙，编写干净的代码，以便将来更轻松地扩展您的应用程序。不要从可扩展性的角度考虑您的设计，而是从模块化和可重用性的角度考虑它，这样到时候扩展应用程序的繁忙部分就不会非常困难。
Right now you should be focussing on the presentation, functionality and security of your application. Scalability comes when you need it -- but do yourself a favor and write clean code to make it easier to scale your application in the future. Instead of thinking about your design in terms of scalability, think of it in terms of modularity and reuseability so that when the time comes it won't be horribly difficult to scale the busy portions of your app.
对于一个目前还没有庞大用户群的Web应用程序来说，一开始功能性肯定比可扩展性更重要。这并不是说您不应该使用也有助于可扩展性的最佳实践，只是您不应该对某些最佳实践进行例外处理，因为它们会损害可扩展性。您可以只专注于正确性和正确的编程，然后如果您的应用程序开始显示可扩展性问题，您可以根据需要修复这些问题。
现在，如果您是 Google，并且推出了 Gmail 或 Google 地图，我认为可扩展性从一开始就应该是重中之重。如果您几乎确信数百万人会使用它，那么您应该在设计（并且绝对测试）时考虑到这一点。
For a web application that doesn't have an existing large user base, functionality is definitely more important than scalability at the beginning. It's not that you shouldn't use best practices that also help scalability -- it's just that you shouldn't make exceptions to some best practices because they hurt scalability. You can just concentrate on correctness and proper programming, then if your app begins to show issues with scalability, you can fix these as necessary.
Now if you're Google, and your coming out with Gmail or Google Maps, I think scalability should be a top priority from the start. If you're almost positive sure that millions of people are going to use it, you should design (and definitely test) with that in mind.