General

•  eZ Systems Website
•  Technical documentation
•  Editor documentation

This Documentation contains:
 
Technical documentation:



⚠ WARNING ! This documentation is deprecated !

Please go to the current Technical Documentation

Versions Compared

Old Version 3

changes.mady.by.user André Rømcke

Saved on

compared with

New Version Current

changes.mady.by.user Dominika Kurek

Saved on

Key

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

...

This page describes the new generation eZ CMS architecture introduced as of eZ Platform and eZ Studio in 2015. However, this architecture has already been battle tested been battle-tested by large multinational companies as part of eZ Publish Platform 5.x series since 2012, for further information previous generation . For further information on the previous generation, see eZ Publish 5 Architecture - Introduction & Overview.

Overview

TODO: Illustration of layers: Symfony > eZ Platform > eZ Studio / Services

...

The following diagram shows a simplistic detailed view of this new architecture, and a more detailed view for developers.

  


The new architecture is layered and uses clearly defined API’s APIs between the layers.

  • The business logic is defined in a new kernel. This business logic is exposed to applications via an API (the Public API). Developers rely on this to develop websites and web applications using Symfony to organize the way they develop the user interface layer.

  • User interfaces are developed using the Twig template engine but directly querying the Public API.

  • Integration of eZ Publish Platform in other applications are is done using the Rest API, which itself relies also on the Public API.

  • finally Finally, the development of extensions of for eZ Publish Platform is done using the Symfony framework when it comes to the structure of the code, and once again relying on the Public API when it comes to accessing content management functions.

To At a lower level, the new architecture also totally redefined the way the system store stores data. while While this is not finalized in version 5.0 (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.

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 all parts of the architecture, at the same time improving the migration capabilities of the system at the same time.