Why is PHP suitable for front-end and JAVA suitable for back-end when learning PHP?

When you see this title, you will inevitably have doubts. Isn’t PHP used for backend? It is really convenient to use a single language. Here, PHP is suitable for the front-end and JAVA is suitable for the back-end, which is aimed at large websites or systems. For example, Taobao's core development language uses JAVA, but the front-end presentation layer uses PHP. Asked again: There are many web development languages, such as Python, Ruby, and Perl. net, why choose PHP?
This is because:
PHP is flexible, quick to get started, easy to modify, and fast to publish. The disadvantages are that it is easy to make mistakes (common such as spelling errors, SQL injection, upload execution, etc.), low execution efficiency, and lack of global cache. The advantages of Java are that it is stable and reliable, has high operating efficiency, and is not easy to make mistakes (strong typing, pre-compilation, must intercept exceptions, etc.). The disadvantage is that the efficiency of development and release is relatively low. This is a relative term here. It does not mean that PHP cannot develop large-scale webs, nor does it mean that JAVA is inefficient. Those with sufficient experience and ability are still very efficient.
Then from the perspective of the MVC hierarchy, in the development cycle of a general website project, the View has the most frequent changes in requirements and the most adjustments, followed by the Controller, and finally the Model. This is very easy to understand. Who changes the data structure every day if they have nothing to do? The control structure has to be changed every time the version is upgraded, more or less. As for View, when will the BU, PM, and UED not be changed in two days?
For communication between the two, RPC technology is currently mature enough. Whether it is Web Service/Hessian/RESTful API, developers can focus on functional development without having to consider too much the differences and differences between heterogeneous platforms. Communication details. This means that the solution of using two languages ​​​​at the same time in a large company does not introduce too much complexity and workload.
In general, close to the user's front-end, using PHP can complete frequent and trivial updates of the front-end faster, and freely respond to changes in various needs. Page structural adjustment, basic verification of user input content, simple logic related only to user interaction, etc. are all suitable for development using PHP. Page changes can even be migrated to the front-end team through template technologies such as Smarty. Basic business logic and data updates are developed using Java, which can effectively improve reusability, improve performance and throughput, and avoid security issues. A slight decrease in development efficiency results in an improvement in maintainability, and slow release speed is not a problem, because usually adjustments to basic business logic are generally modified as a whole, and can only be released after layer-by-layer testing and confirmation.
Therefore, large-scale websites use PHP as the front-end and Java as the back-end, which is easy to recruit and maintain, has a stable system, high performance, and greatly increases security. Code reuse and documentation completeness have also been improved. When you have the above benefits at your fingertips, it is not a problem at all to require a higher breadth of architect's knowledge pedigree.

Why not use a single language:

A single solution can actually achieve good isolation, and PHP can also provide services. In fact, performance problems are often caused by algorithm and architecture problems rather than language differences. question. Such as Velocity or JSTL are also excellent isolation solutions.
But we all know that reality is often much more skinny than ideals. These solutions will expose many problems under high pressure and reflect the advantages of bilingualism. These are actually mentioned above, detailing some of the things that are difficult to change. Points:
1. Due to the characteristics of PHP's dynamic scripting language, classes, functions, and constants need to be repeatedly executed in each request cycle before the operating environment can be established; compilation quality is sacrificed in order to ensure parsing speed; application FastCGI is used, but it only reuses the process to process requests to reduce fork costs, unlike other languages. After initialization, the data is obtained through the FastCGI interface and the data is returned with the corresponding interface. For several reasons, it is basically impossible to recover the original performance in terms of performance. What's even worse is Java who is now driving a JIT brand sports car.
2. It is so easy to make mistakes in PHP and difficult to find. Even if you use the official Zend Studio, it cannot change the fact: to ensure that your program is of high quality and has no major errors, you must have sufficient Experience, sufficient rigor, and responsible QA. Huang Shang from Taobao once joked about IDE. The reason behind the joke "lack of middleware" has been improved a lot in recent years, mainly because the support of many middleware has become more extensive, which has benefited PHP, but the root of its development is still in the C and Java communities. . Performance and error-proneness are technical difficulties caused by language characteristics, and they are also a necessary price for flexibility and speed. It is difficult to expect fundamental improvements.
3. There are also JSTL, Velocity and Freemaker in the Java world, but compared with PHP’s flexible and powerful dynamic capabilities, rich functions and class libraries, easy learning costs, and outrageous documentation, it is simply It’s scum, it’s scum! Is it necessary to restart the Context after changing JSTL? Is it necessary to restart Velocity even if the cache is disabled? Is it possible that Velocity has low performance when caching is turned on? Even if these are ignored, is it necessary to restart the Action when adjusting a certain data verification rule?

Now everyone should have a clear answer to this question.

The above is the detailed content of Why is PHP suitable for front-end and JAVA suitable for back-end when learning PHP?. For more information, please follow other related articles on the PHP Chinese website!