可扩展的Web项目架构
您从哪里获得有关“如何构建可扩展的高性能 Web 应用程序”的信息？我的意思是架构、最佳实践等。无论平台和语言如何：.net、php、java ... 您是否在项目中遇到了自己的“史诗般的失败”，然后在几个晚上重构了系统或从互联网获取信息？
有没有什么社区可以让我分享自己的经验并得到一些回应？
是的，我知道每个项目都是单独的。
Where do you get info about 'how to build scalable, high perfomance web app'? I mean architecture, best practice ets. regardless of platform and language: .net, php, java ...
Did you get your own 'epic fails' in your project and then refactor your system in a few nights or get info from internet?
Is there any communities where I could share my own expirience and get some response?
Yeah, I know that every project is individual.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您可以阅读高可扩展性博客。如果您对架构和可扩展性有疑问，您可以随时使用 StackOverflow，除非问题是主观的。
You can read the High Scalability blog. If you have questions about architechture and scalability, you can always use StackOverflow unless the question is subjective.
回答这个问题并不容易。在考虑可扩展性时，语言和平台处于次要地位。
“可扩展性实际上是系统的一个属性，而不是该系统、基础设施的单个层。即使拥有最好、最性感、最自动的扩展层，您也可以轻松编写无法扩展的代码。- glyph< /em>"
然而，您可以在
It is not easy to answer this question. Language and Platform takes a secondary place when thinking about scalability.
"Scalability is actually a property of a system, not an individual layer of that system, infrastructure. Even with the best, sexiest, most automatic scaling layer, you can easily write code that just doesn't scale. - glyph"
How ever, you can immerse into a very good collection of resources on this issue at
仅关注可扩展 Web 架构的 Web 部分，您可能需要查看一下您应该这样做的 7 个原因使用 XMPP 而不是 AJAX，尤其是当您的 Web 应用程序需要通过大量实时社交功能进行扩展时。
Just focusing on the web part of scalable web architecture, you might want to take a look at these 7 reasons why you should be using XMPP instead of AJAX especially if your web app needs to scale with lots of real-time social features.