Navigation
eZ Documentation Center
 

This is outdated documentation made for eZ Publish Platform 5.2. It is being moved into the eZ Publish 5.x documentation, so please go there for most up-to-date documentation.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

eZ Publish Technical Architecture

With the 5.0 2 release eZ Publish is making an important leap forwards in terms of technology.
This document will explain why we are renewing our technology platform, and to some degree explain what this evolution in architecture means to eZ Publish developers and users, and last but not least how eZ Systems is affected by these changes.

...

In order to meet performance and scalability requirements, eZ introduces new storage systems with the version 5 serie. In 5.02, this storage system lives beside the legacy storage system and data model, but will use the new API to access the data. Also in 5.0 2 version, this new storage engine only support Mysql relational database, nevertheless it is designed to allow the development of drivers for other storage engines through the Persistence SPI (service provider interface) and in the future will include drivers for NoSQL and Document based storage engine. The ultimate goal is to open for custom storage developments.

...

To a lower level, the new architecture also totally redefined the way the system store data. while this is not finalized in version 5.0 2 (where the new storage system is only shipped with mysql support), the architecture, when finalized will rely on a storage api that will be used to develop drivers to any kind of storage subsystem.

...

On its side, the new architecture has been implemented, and eZ will implement new features and applications on top of it subsequently. So, as part of 5.02, the new architecture is in place, but does not provide yet the full application scope.

...

These two ways to implement a compatibility between the past architecture and the new one offers a wide range of possibilities and a smooth transition path.


 

Summary on the ways to use eZ Publish 5.

...

2


Using eZ Publish 5.

...

2 in full legacy mode

This way is the less disruptive. In this way, eZ Publish 5.0 2 totally behave as if it was an eZ Publish 4.7, or we should say 4.8. This is ideal for users who have large existing applications with large amount of data and who are not willing to invest in learning and migrating them immediately.

...

In this way, even the siteaccess and vhost configuration bypass the legacy stack, and developers will see almost no differences.

  


 

Using ez publish 5.

...

2 through the legacy stack but relying on the new controller and new template system as well as the new kernel.


 

This way offers a transition and allows to combine old template and new templates in the same application. In this case, the users will rely on the administration interface of eZ Publish as well as on the ez tool bar for front-end editing, through the legacy templates, but the front end will be either based on legacy or new twig based templates.

...

  • the administration interface is not available in 5.02

  • existing templates and site won’t run without having been migrated

  • the old storage system is not used any more

...