=20
=20
=20
=20
=20
=20
=20
This page describes the new generatio= n eZ CMS architecture introduced as of eZ Platform and eZ Studio = in 2015. However, this architecture has already been battle-tested by = large multinational companies as part of eZ Publish Platform 5.x = series since 2012.
eZ Platform Architecture details
The architectur= e is layered and uses clearly defined APIs between the layers.
The business logic is defined in a n= ew kernel. This business logic is exposed to applications via an API (the <= span style=3D"color: rgb(0,0,0);text-decoration: none;">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
Integration of eZ Platform in other applications is d= one using the &nbs= p;Rest A= PI, which itself relies also on the = Public API.
Finally, the development of extensions for eZ Platfor= m 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.
At a lower leve= l, the new architecture also totally redefined the way the system stores da= ta. While this is not finalized in version 5.0 (where the new storage syste= m is only shipped with MySQL support), the architecture, when finalized wil= l rely on a storage API that will be used to develop drivers to any kind of= storage subsystem.
A motto for thi= s new architecture is to heavily use APIs that will be mai= ntained on the long term to ease upgrades and provide lossless coup= lings between all parts of the architecture, at the same time improving the m= igration capabilities of the system.
=20
=20
=20
=20
In this topic:
=20
=20