The session will be more relevant for back-end developers of any skill level. It is also informative for beginners who wish to know about Decoupled or headless architecture.
Can any architecture provide breakthrough user experiences? Or is there any way to give developers great flexibility to innovate, and help site owners future-proof their builds by allowing them to refresh the design without re-implementing the whole CMS ? The solution is Decoupled or headless CMS architecture which is gaining great popularity in the development world.
The session will include sharing of my last project experience which used a decoupled and dis-joint architecture solution based on the three-tier architecture approach, which separates back-office operations, logical decisions and frontend presentation layers. The solution includes:
Moving the Drupal Content Management System to the back-end from a web architecture perspective while keeping it as a “business system” for managing the contents for the site.
Frontend will be served through two major components Slim and twig. Slim will be used as server to serve web pages, routes processing. Twig will be used as client and server side templating engine.
The process of page rendering is dependent on Logic Layer, which will act as a data exchange bridge between Drupal and Frontend. Redis server will be used to cache the response.
Any page component which do not change frequently will be processed and cached at server side. The rendered output will be used in the final page template.
Objective of the Session:
- Problem statement of the project for which decouple architecture was proposed.
- Understanding Decoupled Architecture
- Why does decoupled CMS matter
- How to use web services for creating connections in fully decoupled architecture
- Demonstration of the Decouple Architecture
My session will talk something new about headless architecture, and hopefully entertain as well as enlighten you on our journey to take Drupal to new level.