For the PHP development framework

some View

Since the birth of php by the vast number of programming enthusiasts like to become a good helper of small and medium-sized webmaster, and training a large number of PHP programmers, but with the more extensive application of PHP, many times has not been limited to small and medium-sized web site applications, some large PHP projects are not uncommon.

when we choose PHP Development

large projects, you have to consider the development of efficiency, development norms, post-maintenance and other issues, at this time people will often choose a recognized development framework, the current popular Zend Framework, Yii, Symfony, CodeIgniter, cakephp, etc. all claim to have the ability to develop large-scale applications.

New frameworks are emerging, but when we really apply these frameworks to product implementation, there are always different problems:

a large framework behind often has a deeper structural theory, the most familiar is MVC, ORM, and so-so-familiar theoretical terminology, there are many deep object-oriented knowledge, but there are few people who really understand these, so that the threshold of application has risen sharply, in addition to this large framework of application details are complex, the study cost is relatively high, This is especially embarrassing for PHP, which is intended to locate small and medium-sized applications.

Second, PHP as a scripting language, it is often run based on the host process (such as: Apache, PHP-FPM), on a single request through the creation process, initialization environment, compilation scripts, run engine, output, resource recovery, process destruction and a series of processes, At the programming language level, the efficiency of integrated operation is slower than the compiled language 2-3 orders of magnitude, along with the consumption of a large number of system resources, on this basis we also build and load complex development framework is to increase its operating costs. In large applications, there is no shortage of special requirements, and sometimes PHP's larger-scale framework is deadly.

Three, the large framework to consider too many factors, developers need to pay extra attention to the code in the application of excessive detail, such as: Non-standard conventions, lengthy manuals, trivial configuration, complex file directory structure, difficult to restrict the rationality of constraints, the different kinds of library and so on, so that most programmers development process is often bad confusion, Improving the efficiency of development has also become empty talk.

The most deadly point, the framework author is constantly looking for silver bullets, trying to make a monster that meets all needs. Large applications require a high level of loose coupling to the system, and it is often not possible to operate directly on the development plane, see a simple SOA model (the drawings), the data layer and the business layer are almost physically isolated, and the business layer is developed for only the service interfaces provided by the data tier. From the current PHP development framework (especially the MVC model), it is common to use ORM to abstract database tables directly and to CRUD operations directly, and the large-scale applications will not do this (perhaps for VPS, but large applications will choose VPS??). ）。

Summary, PHP Large framework really is still in a very awkward position, but on the other hand, good PHP large framework is really a great example worthy of learning, which contains a large number of design concepts, design patterns, code optimization, language features, software engineering and other knowledge systems, blending PHP essence but far beyond PHP itself.

in the end, these large PHP Framework

Say a popular word, "the one who learns, the one who dies."

For the PHP development framework