...
| Simplified view | Detailed view |
|---|---|
  |  |
The new architecture is layered and uses clearly defined API’s between the layers.
...
The chapter above is only explaining the new architecture but, as mentioned, version 5 also offers a way to run the legacy eZ Publish stack, in order to simplify upgrade and switch to version 5. This result in the end in a more sophisticated architecture that is illustrated in the diagram below.
The main difference is, the cohabitation between the new architecture explained in the previous chapter (on the right) and the previous architecture (on the left).
...
In this way, even the siteaccess and vhost configuration bypass the legacy stack, and developers will see almost no differences.
Using ez publish 5.0 through the legacy stack but relying on the new controller and new template system as well as the new kernel.
...
In this model, the two kernels can be used and the system can this way benefit from the Public API and the new REST API built on top.
Using the brand new "Platform"architecture only
...
In the context of eZ Publish 5, it can be useful for new projects relying only on the concept of "content as a service" the platform is a high performance and scalability content repository with very advanced services but provide no editorial user interface. for traditional content management.
| Info | ||
|---|---|---|
| ||
Learn more with this video : |