Global navigation

   Documentation Center
   eZ Studio & eZ Platform
     User Manual
     Technical Manual
   eZ Publish 4.x / legacy

eZ Publish (5.x)

eZ Publish 5.x | For eZ Platform & eZ Studio topics see Technical manual and User manual, for eZ Publish 4.x and Legacy topics see eZ Publish legacy

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update to reflect "Platform" term more clearly


eZ Systems is now introducing the following as the new "Platform":

  • An extended and sustainable Public API. This will speed up developments on the platform and improve their quality and maintainability both for eZ core developers and extension developers, which in turn will lead to more efficient implementation projects

  • An improved REST API with read and write functionality and support all the core content management functionality.  This way, eZ Publish will better integrate with any programming framework, for instance into mobile applications or any other web application. Better meaning faster and simpler. in order to fulfill the multichannel vision and execute on the User Experience demands and needs of customers and users of the eZ Publish platform

  • Introducing Symfony as the PHP framework under the platform to make developers lives easier and to make developments on eZ Publish accessible for more developers to further support innovation in eZ Publish

  • Introducing Twig as the template engine to simplify working with templates in eZ Publish. And as a standard template engine this will also make eZ Publish templating accessible to more developers

  • Introducing a new storage system for scalability, performance and maintainability reasons


  •  Introducing a backward compatibility between the new "Platform" architecture resulting from the above and the "legacy" architecture as known in eZ Publish 4.x


In order to meet performance and scalability requirements in the future, eZ introduces new storage systems with the version 5 serie.


Understanding the architecture in more detail

The target architecture: "eZ Platform"

The first important thing to understand about the new architecture is to explain it standalone, without considering the old legacy architecture.


A motto for this new architecture is to heavily use APIs that will be maintained on the long term to ease upgrades and provide lossless couplings between each part of the architecture, improving the migration capabilities of the system at the same time.

The "real" version 5.x architecture: "Legacy" and "Platform" together

The chapter above is only explaining the new architecture but, as mentioned below, 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.


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

This case is the one that will deliver very strong improvements in scalability and performance, in this case the whole new architecture is used and there is no way to reuse components from the legacy architecture.


  • the administration interface is not available in 5.0

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

  • the old storage system is not used any more

 Note: because of these restrictions, a new storage engine has not been made yet. Similar setup can use the "Legacy storage engine" for the time being to be ready to migrate data and not have to change code when a new engine is added in the future.

While this might sound restricting for the time being, it is clearly the foundation of the future of eZ Publish.