Slide 1

Slide 1 text

Decoupled Drupal PRESENTED BY Rohil Mistry

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

Decoupled Architecture 4 Source: https://www.acquia.com/blog/headless-drupal

Slide 5

Slide 5 text

Advantages of Decoupled ● Reusable capabilities of the Content ● Significant Performance Improvement ● Reduced cost of redesigns ● Supports multiple consumer ● Expedited Development 5

Slide 6

Slide 6 text

Challenges of Decoupled ● Higher Development Cost ● Technical Complexity ● Multi-site Difficulty ● Content Model Lock-in ● Less page control 6

Slide 7

Slide 7 text

Decouple or Traditional: How to decide? 7 Source: https://dri.es/how-to-decouple-drupal-in-2019

Slide 8

Slide 8 text

Decoupled Drupal Example ● Let’s assume requirement is to build architecture/infrastructure for Multi-site Decoupled Drupal. ● What would be your generic architecture? 8

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

Questions? 10

Slide 11

Slide 11 text

11