可扩展的票务/节日网站
我注意到大型音乐节（至少在澳大利亚）和其他在门票发售时经历流量高峰的活动在保持其网站良好运行方面存在巨大问题。我见过一些不同的技术来尝试解决这个问题，例如短会话和虚拟队列，但它们似乎没有太大效果。
如果您要设计一个网站在短时间内出售大量门票，您将如何处理可扩展性？您会使用哪些技术和编程技巧？
我的经验是在 Microsoft 堆栈中，因此该领域的答案对我来说最有用，但我也想听听如何在其他平台上解决此类问题。
I've noticed major music festivals (at least in Australia) and other events that experience a peak in traffic when tickets go on sale have huge problems keeping their websites running well. I've seen a few different techniques used to try combat this such as short sessions and virtual queues but they dont seem to have much effect.
If you were to design a website to sell a lot of tickets in a short amount of time how would you handle scalability? What technologies and programming techniques would you use?
My experience is in the Microsoft stack so answers that in that area will be most useful to me but I'd also like to hear how this sort of problem could be solved on other platforms.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为主要问题不在于让这样的系统具有可扩展性“困难”，而在于 99% 的情况下，这些网站没有太多流量。购买 50 台前端服务器和 10 台数据库服务器如果 99% 的时间都处于闲置状态，那就没什么好处了。
就我个人而言，我会使用 Amazon EC2 甚至微软的新 Azure 服务之类的东西，这样它们就可以在大多数时间以最小的容量运行，然后在大型活动开始销售之前增加容量。
I think the main problem is not that it's "hard" to make such a system scalable, it's that 99% of the time, those sites don't have much traffic. It's not much good buying 50 front end servers and 10 database servers if 99% of the time, they're all idle.
Personally, I'd use something like Amazon EC2 or even Microsoft's new Azure service so that they can run with minimal capacity most of the time, and then ramp up just before a big event goes on sale.