Decoupled Drupal

Drupal decoupled for the headless CMS

Transcript

1. Decoupled Drupal PRESENTED BY Rohil Mistry
2. Agenda • What is Decoupled Drupal? • Decoupled Architecture • Advantages of Decoupled • Challenges of Decoupled • Traditional or Decoupled: How to decide? • Decoupled Multi-site example with Architecture 2
3. What is Decoupled Drupal? • Decoupled or Headless Drupal is nothing but a separation of the Backend and Frontend where Drupal will act as a Content repository that stores and manages data just like a traditional Drupal Installation. • Content will be served to the Front end via APIs. 3
4. Decoupled Architecture 4 Source: https://www.acquia.com/blog/headless-drupal
5. Advantages of Decoupled • Reusable capabilities of the Content • Significant Performance Improvement • Reduced cost of redesigns • Supports multiple consumer • Expedited Development 5
6. Challenges of Decoupled • Higher Development Cost • Technical Complexity • Multi-site Difficulty • Content Model Lock-in • Less page control 6
7. Decouple or Traditional: How to decide? 7 Source: https://dri.es/how-to-decouple-drupal-in-2019
8. Decoupled Drupal Example • Let’s assume requirement is to build architecture/infrastructure for Multi-site Decoupled Drupal. • What would be your generic architecture? 8
9. Decoupled Drupal Architecture 9 Visitor CloudFront CDN S3 Bucket with Front End App + Static Assets API Gateway Lambda function – Proxy API Decoupled Drupal Acquia Servers Image Assets Editor
10. Questions? 10