解决可扩展性问题
我最近转向了一个名为 Yii Framework 的框架。在框架上工作真的很好,解决了很多平凡的工作。我相信该框架将为我提供构建出色网站的平台,但高级开发人员不断问我这些问题。网站可以处理多少并发用户?
该网站是否可扩展?
网站的性能水平如何?
如果您要回答有关您的项目的这些问题,您会怎么做?
以及您将如何一劳永逸地解决可扩展性问题。
PS 任何我可以阅读的参考文献都将受到极大的欢迎。
I have recently made the shift to a framework called the Yii Framework. Really is good to be working on a framework, solves lot of mundane work. I believe the framework will provide me the platform to build a great site but a senior developer keeps asking me these questions.How many concurrent users can the site handle?
Is the site scalable?
What is the performance level of the website?
If you were to answer those questions about your project how would you do it?
and also how would you tackle the scalability issues once and for all.
P.S. Any references i could read upon will be greatly welcome.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
可扩展性并不是一个可以堵住的漏洞。它本身就是一个非常广泛和通用的主题。我见过的最好的方法之一是 youtube
话虽如此,数据库通常是大多数Web应用程序和Web框架的选择并不重要。对于大多数框架来说,并发用户数量和性能水平等都足够大。
虽然这个答案已经很晚了,但我希望它对您未来的项目有所帮助。
Scalability is not a hole that one can plug. It is a very broad and generic topic in itself. One of the best approaches I've seen is that of youtube
Having said that, database is usually the bottleneck in most of the web applications and the choice of web framework doesn't matter much. Things like number of concurrent users and performance levels will be sufficiently large for most of the frameworks.
While this answer is quite late, I hope it helps you in your future projects.
您不应该将可扩展性视为创可贴或一次性修复。
随着应用程序的使用情况发生变化,您的可扩展性需求也会发生变化和发展。此外,解决可扩展性问题也没有灵丹妙药。它是各种方法的组合,如缓存、复制、分发、性能调整、硬件升级等。您应该根据“您想要扩展的内容”的上下文来选择这些方法,以及在哪里可以获得最大的性价比!
查看此链接
http://sevenoct.wordpress.com/2013/07/04/scaling- applications/
其中有一些关于可扩展性以及如何不陷入“受追捧”的可扩展性口号的陷阱的好信息
You should not look at scalability as a bandaid or a one time fix.
As the usage of your application changes, your scalability requirements will change and evolve. Also, there is no silver bullet for addressing scalability. It is a mix of various approaches like caching, replication, distribution, performance tuning, hardware upgrades etc. You should choose from those based on the context of "what you want to scale" and where will you get maximum bang for the buck!
check out this link
http://sevenoct.wordpress.com/2013/07/04/scaling-applications/
which has some good information about scalability and how not to fall into traps of "sought after" scalability mantras