blocks|key|3855891|text|这个问题已经被问过很多次了。普遍的共识是总是做你能做的事情。不要担心从一开始就让它变得太可伸缩，只需稍微记住它。试图从一开始就构建可伸缩性太强的代码会让人精疲力竭，而且你很可能会放弃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3855892|如果你真的因为大量的人气而开始遇到问题，那就太好了！然后你就会变得足够受欢迎，希望能赚到足够的钱，开始担心支付更昂贵的托管和更高端的编程/数据库框架和引擎。|3855893|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

This question has been asked many times. The general consensus is always do what you can do. Don't worry about making it too scalable from the start, just keep it in your mind slightly. Trying to build too scalable from the start is exhausting and you would most likely give up.

If you do start getting problems due to massive popularity, thats great! You are then popular enough and hopefully earning enough to start having to worry about paying for more expensive hosting and higher end programming/database frameworks and engines.

blocks|key|2542804|text|从头开始构建它。在优化时，控制每一位都有帮助。Facebook甚至控制它的php编译器：http://developers.facebook.com/blog/post/358/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2542805|不要使用框架，因为PHP已经是一个框架和模板引擎：http://toys.lerdorf.com/archives/38-The-no-framework-PHP-MVC-framework.html|2542806|使用一些缓存库，比如memcached。我不确定你是否可以在云上使用它，或者云可能会提供自己的缓存系统。|2542807|entityMap|0|LINK|mutability|MUTABLE|url|http://developers.facebook.com/blog/post/358/|1|http://toys.lerdorf.com/archives/38-The-no-framework-PHP-MVC-framework.html^0|18|19|0|0|P|23|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Build it from scratch. Controlling every bit helps while optimizing. Facebook even controls its php compiler: <a href="http://developers.facebook.com/blog/post/358/" rel="nofollow">http://developers.facebook.com/blog/post/358/</a>

Do not use a framework since PHP is already a framework and a template engine: <a href="http://toys.lerdorf.com/archives/38-The-no-framework-PHP-MVC-framework.html" rel="nofollow">http://toys.lerdorf.com/archives/38-The-no-framework-PHP-MVC-framework.html</a>

Use some caching library like memcached. I'm not sure if you can use it on the cloud, or the cloud may provide its own caching system.

blocks|key|3855926|text|如果您知道您很快就需要扩展它，那么使用现有的成熟框架是一个好主意，而不是从头开始构建您自己的框架。与其说是为了可伸缩性，不如说是为了简化您以后的工作，并对样板代码足够好的功能有更大的信心。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3855927|另一方面，如果您从未使用过上述框架中的任何一个，则可以考虑权衡需要超过初始学习曲线的时间。|3855928|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you know you will need to scale it soon, then it's a good idea to use existing proven frameworks, rather than building your own from scratch. Not so much for the scalability, but more to simplify your work later, and have greater confidence that boilerplate code functions well enough.

On the other hand, if you have never used any of the mentioned frameworks, you might consider weighing the time you will need to overpass the initial learning curve.

blocks|key|2542787|text|投入比平时更多的精力来确保您的域层与其余代码尽可能松散耦合-这样，如果您发现其他层存在问题，您应该能够敞开大门进行更改。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2542788|一定要使用框架来启动和运行，但要注意使用他们自己的CRUD实用程序(CI，我正在看着你)。|2542789|如果您决定要使用ORM解决方案，那么可以选择一种可以很好地与许多框架配合使用的解决方案。|2542790|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Put more effort than usual into making sure your domain layer is as loosely coupled as possible from the rest of the code - that way you should be able to leave the door open to change if you identify problems with the other layers.

Use a framework by all means to get up and running but beware of using their own CRUD utilities (CI, I'm looking at you).

If you decide you want to use an ORM solution, then maybe choose one that plays nicely with a number of frameworks.

blocks|key|2542774|text|如果你从头开始构建每一件事，那么肯定需要时间，但只有你才会知道代码的内部逻辑。相反，如果你使用一个框架，你会得到快速的开发，但在这种情况下，你是在代码上制作你的网站，这意味着更多的机会被黑客攻击。每种方法都有自己的优点和缺点。无论如何，你可以看看php+Top+10+frame+works+of+PHP最好的框架。我推荐Code+Igniter|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2542775|entityMap|0|LINK|mutability|MUTABLE|url|http://www.phpframeworks.com/top-10-php-frameworks/|1|http://codeigniter.com/^0|3J|P|0|4H|C|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

If you build each and every thing from scratch then for sure it will take time but only you will know the internal logic of code. In contrast if you use a framework you will get quick development but in that case you are making your website on that code which is opened for any one means more chances to be hacked. Each method has its own pro and corns. Anyway you can check out best frameworks of php <a href="http://www.phpframeworks.com/top-10-php-frameworks/" rel="nofollow">Top 10 frame works of PHP</a>. And I would recommend <a href="http://codeigniter.com/" rel="nofollow">Code Igniter</a>

blocks|key|75705|text|我会说不，因为现在有更好的语言。Ruby和C#拥有比php更好的命名空间和开发工具。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|75706|然而，你真正的问题并不是语言。它将是数据库层，因为这将更加集中。您可以使用memcached来减少数据库的负载。如果您正在使用ORM，请检查它是否具有运行直接查询和运行批量插入的所有能力，或者使用连接而不是延迟加载的查询来获取相关对象。|75707|您还应该使用队列来加快页面加载速度。如果您的操作很慢，可以在页面请求之外完成，那么可以将它们推入队列中，稍后再处理它们，可能是在不同的服务器上。电子邮件和图像大小调整就是一个很好的例子。|75708|如果你想要一个真正可伸缩的web应用程序，你必须走出Apache，MySQL泡沫，开始使用像Nginx和非关系型数据库这样的工具。|75709|就目前而言，最好的做法是，在问题出现之前不要太担心它。只要确保您选择的任何框架都是松散耦合的，这样您就可以做一些事情，比如切换数据库层。避免像瘟疫一样的codeigniter，它根本不是模块化的，也没有ORM和一个非常糟糕的形式库。我推荐Django(python)，有很多公司为它做云托管。我见过一家商店从PHP切换到Python，他们最终非常喜欢它。不要认为你必须被PHP所束缚，特别是当你选择托管的时候。|75710|编辑，回复卡通姜戈。但是如果你真的想要PHP，也许可以使用Symfony，但它以速度慢而闻名。kohana类似CI，但更多的是社区驱动和OOP，所以codeigniter的一些主要缺陷很久以前就在Kohana中得到了解决。我也听说过关于Cake的好话，但我自己从来没有品尝过。至于codeigniter，是的，很多人喜欢它，它很简单，但缺乏许多好的软件模式，支持丑陋的快捷方式。我使用它工作了一年，过了一段时间，团队中的每个人都同意我们重新发明了太多的轮子，需要一些其他的东西。当你使用它一段时间后，问题就开始浮现出来。我们争论了一段时间，最终最终选择了Django。这是一个艰难的决定，但回报是更高的生产力。再加上谷歌使用它，我认为这说明了很多问题。|offset|length|style|BOLD|75711|认真地说，python是comp+sci+101课程中仅有的几种专业语言之一。python的目标之一是使comp+sci的教学变得简单。这并不可怕，打开一个终端，输入python，然后玩一玩。也有很多很好的工具，比如pip，它类似于PHP-pear，但也可以使用git、gzip、hg和许多其他格式，除了出色的python包存储库。还有一大堆包都是为它准备的，我在PHP中几乎看不到。http://djangopackages.com/|CODE|75712|至少给它一个机会，通过做教程，这需要大约2个小时。它有一个内置的web服务器，所以除了python本身，没有什么需要设置的。|75713|http://docs.djangoproject.com/en/1.3/intro/overview/|75714|entityMap|0|LINK|mutability|MUTABLE|url|http://djangopackages.com/|1^0|0|0|0|0|0|0|7|0|2B|6|5C|Q|0|0|0|0|1G|1|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@$L|1B|M|1C|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1D|8|@$L|1E|M|1F|N|R]]|9|@$L|1G|M|1H|1|1I]]|A|$]]|$1|S|3|T|5|6|7|1J|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1K|8|@]|9|@$L|1L|M|1M|1|1N]]|A|$]]|$1|W|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|V]]]]

I would say no because there are better languages today. Python, Ruby and C# have much nicer namespacing and development tools than php.

Your real problem however will not be the language. It will be the database layer, since this will be a lot more centralized. You can use memcached to reduce the load on the database. If you're using an ORM check that it has all the ability to run straight queries and run bulk inserts or use joins rather than lazy loaded queries to get related objects.

You should also use queues to speed page loads up. If you have slow operations that can be done outside of the page requests then push them into a queue and process them later, possibly on a different server. Emails and image resizing is a good example.

If you want a truely scalable web application you will have to step outside the Apache, MySQL bubble and start using tools like Nginx and non-relational databases.

For now, what it is best to do, is not worry too much about the problem before it even exists. Just make sure whatever framework you choose is loosely coupled so you can do things like switching out the database layer. Avoid codeigniter like the plague, it isn't modular at all and has no ORM and a really poor form library. I would recommend Django(python), there are a number of companies which do cloud hosting for it. I've seen a shop switch from PHP to Python and they ended up liking it a lot. Don't think you have to be locked into PHP, especially when you are choosing the hosting.

Edit, reply to Cartoonle
Django. But if you really want PHP, maybe Symfony, but it is known for being slow. Kohana is like CI, but more community driven and OOP, so some of the major flaws of codeigniter have been solved long ago in kohana. I've also heard nice things about Cake, but never tasted it myself. As for codeigniter, yes many like it, it is simple, but lacks a lot of good software patterns in favor of ugly shortcuts. I worked with it for a year, after a while everyone on the team agreed we were re-inventing the wheel too much and needed something else. When you've worked with it for a while the problems start to bubble up. We debated for a while, eventually ended up with Django actually. Was a hard decision but paid off with higher productivity. Plus Google use it, I think that says a lot.

Seriously python is one of the only languages used in comp sci 101 courses and professionally. One of the goals of python was to make teaching comp sci easy. It's not that scary, open up a terminal, type in <code>python</code> and have a play around. There are a lot of nice tools around for it too, like pip, which is like PHP-pear but also works with git, gzip, hg and a number of other formats besides the wonderful python packages repository.
There is also a heap of packages around for it, which I really don't see nearly as much with PHP. <a href="http://djangopackages.com/" rel="nofollow">http://djangopackages.com/</a>

At least give it a chance by doing the tutorial, which takes ~2 hours. It comes with a built in web server so there is nothing to setup besides python itself.

<a href="http://docs.djangoproject.com/en/1.3/intro/overview/" rel="nofollow">http://docs.djangoproject.com/en/1.3/intro/overview/</a>

We are preparing to build a web site with high scale potential. If the scale comes, we want to be ready for it! We decided to use PHP, Apache and MySQL. Should we use some kind of PHP framework (PHPulse, CodeIgniter, CakePHP, Zend,...), or it's better to build everything from the scratch?
The nature of web site will be similar to Facebook, but there will be mostly text data (not many images, videos). Web site will be hosted on cloud.

What would you recommend?

Regards...

Should we use PHP framework for a high scalable web site?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们正在准备建立一个具有高规模潜力的网站。如果规模来了，我们要做好准备！我们决定使用PHP，Apache和MySQL。我们应该使用某种PHP框架(PHPulse，CodeIgniter，CakePHP，Zend，...)，还是从头开始构建一切更好呢？网站的性质将类似于Facebook，但将主要是文本数据(不是很多图像，视频)。网站将托管在云上。你有什么推荐的？致敬..。

问对于一个高度可伸缩的网站，我们应该使用PHP框架吗？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于一个高度可伸缩的网站，我们应该使用PHP框架吗？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于一个高度可伸缩的网站，我们应该使用PHP框架吗？
EN