I found that many php frameworks use a single portal, but basically I have seen open-source systems such as discuz, zencart, and destoon, do companies generally write their own projects at a single portal? I found that many php frameworks use a single portal, but basically I have seen open-source systems such as discuz, zencart, and destoon, do companies generally write their own projects at a single portal?
Reply content:
I found that many php frameworks use a single portal, but basically I have seen open-source systems such as discuz, zencart, and destoon, do companies generally write their own projects at a single portal?
A single portal is easy to implement pseudo-static, convenient to control program processes, and more complex architecture
As the elders like discuz did not have a mature architecture and object-oriented thinking in the past development process, it is not reflected in this aspect.
The old generation of open-source systems used the mature process-oriented development model that was also the strength of php. programmers at that time wrote projects in that way. After a project matures, it is very costly to change the architecture, so they have been using it all the time. If you have some new open-source code, you will find that you have adopted the single portal you mentioned, such as the open-source store prestashop, which can easily perform request verification and so on.
Think of a website as a small country. A single portal is equivalent to a Head of State. Multiple portals are equivalent to a country without a head of State, a programmer (God) we can simply tell this head of state what we need to do. For the multi-element head (equivalent to no head of State), the efficiency is obviously not that high. In fact, a single portal is also a multi-portal, just abstract a single portal on the basis of these multiple portals. These multi-entries can be understood as multiple classes, and a single entry is their parent class.
It is not conducive to SEO and is not used by General websites.