Answer the question
In order to leave comments, you need to log in
CMS in PHP...........?
Tell me: is it worth writing cms in “pure” php or is it better to use the CodeIgniter framework?
Task: write sms for a site with high traffic.
We will use apache and mySQL5.
Or please advise your version of the framework for this task.
Thank you.
Answer the question
In order to leave comments, you need to log in
I'll be brief: Yii . In general, the topic is chilling. For example, what do you have a large attendance?
On pure php, it’s not worth it, if only because the development costs will be much higher, and the profit in terms of performance is very doubtful.
I'm joining Yii, you can also look at various micro-frameworks.
But generally speaking, performance will primarily depend on the right architecture, on the right use of caching, on query optimization, and to a much lesser extent, on the framework.
A framework is primarily a set of rules. If the team adheres to it, it’s good, if not, the gamnocode and brakes will start in any framework.
If you have a competent architect, make your own frame.
Regarding the cost of development and servers - Hardware for a hiLoad project costs about $ 30,000. Calculate for yourself what will come out cheaper - immediately make a fast frame, or pay more for servers later.
zend. given where he got his legs from, he has a chance to defeat everyone sooner or later.
an additional bonus is that it is the most "framework", other frameworks are more "tsms-ionized", in the sense that zend can be connected in parts, in the necessary parts.
100 per second? This is 3000 active threads (the standard Apache setting with a timeout, sort of), which are constantly recreated, allocate and give 10-20 MB of memory each ...
I would not advise you to do it on Apache, muscle and peh - unless, of course, you can "horizontally" scale the service, i.e. use multiple virtual machines.
The overhead of running processes in this bundle is very high. It is better to choose some asynchronous solution, for example, in Java.
Or at least another web server.
On any system, if the write is once per minute, and 100 times per second is passive browsing, nginx can save with a minute of caching. and it doesn't matter what the framework is. there were a couple of articles on the subject. Our record is about 3000 per second on a weak VDS.
No problem, do it under CodeIgniter, a very light and not overloaded framework, a lot of third-party modules, and the standard distribution has the necessary modules. Caching is all possible means.
In your bundle and 100 per second, I would take care of how to remove apache, replace it with nginx, how to install varnish, and where to store the cache, memcache for example.
Hint: you should not write cms in "pure" php.
Moreover, take a look at the solutions available on the market ( PyroCMS - from one of the CodeIgniter contributors, yes, thousands of them ...), run load tests, make a decision.
For high-speed frameworks, I want to note FuelPHP (also from CodeIgniter contributors). According to some unverified data, it's faster than Yii :)
All of the above - IMHO, see for yourself on the task at hand. Hope it helped in some way
ZF2, in tests much faster than ZF1, rewrote and rethought many problem areas. In addition, as mentioned above, it was originally sharpened for php 5.3.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question