Web Farm 应用程序部署最佳实践
我们有一个托管多个 ASP.Net 应用程序的网络场。我们的服务器场中通常有 4 台服务器。
我面临的困境是农场的容量问题。假设我目前总共有 200 个应用程序。我应该在所有 4 台服务器上部署所有 200 个应用程序（即场中的所有服务器都是相同的），还是应该将应用程序拆分到 2 组服务器之间并创建 2 个较小的场，以便我可以根据应用程序的重要性和用途等
We are having a web farm which hosts multiple ASP.Net applications. We typically have 4 servers on the farm.
The dilemma which i am having is in terms of capacity issue of the farm. Lets say i have currently got 200 apps in total. Should I deploy all 200 apps on all 4 servers (i.e. all the servers in the farm are identical) or should i split the applications between 2 sets of server and create 2 smaller farms so that i can then manage the application based on its criticality and usage etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这还取决于处理每个应用程序需要多少服务器，以及您的更新方法。
如果应用程序需要两台服务器来处理负载，那么您可能会认为可以按照您描述的方式拆分应用程序。但是，如果您需要在升级期间保持完整的服务，则需要第三台服务器（这是 N+1 冗余）来确保两台服务器始终能够处理负载。
由于这样的事情，我将在所有服务器上部署所有应用程序，并使用负载平衡器（假设您有它们）来处理服务器之间的实际负载分配。这可以让您在大多数时间为高级应用程序（甚至高级用户）提供更多可用资源，但可以让您在峰值负载、更新等期间重新分配。
您可能也应该在 webmasters.stackexchange.com 上问这个问题
This also depends on how many servers are needed to handle each application, and on your approach to updates.
If an app requires two servers to handle the load, then you might think you can split the apps in the way you describe. But if you need to maintain full service during upgrades, you need a third server (this is N+1 redundancy) to ensure two are always up to handle the load.
Because of things like this, I would deploy all applications on all servers, and use the load balancers (assuming you have them) to handle tha actual distribution of load across the servers. This lets you give premium apps (or even premium users) more of the available resources most of the time, but lets you re-allocate for periods of peak load, updates etc.
You should probably ask this question on webmasters.stackexchange.com too