Decoupling 101

on YouTube ↗29m

" summary

Claims that decoupling makes teams smaller and swappable are backed by specific stacks: a Drupal backend serving an abstract API consumed by JavaScript front ends like Gatsby or React, deployed as separate apps (multi-app on Platform.sh). Progressive decoupling appears as widgets layered onto an existing Drupal front end. Costs include doubled tests, separate security, and significant API work. Concrete wins: a film festival migration becomes 100% online festival and Open Social builds a decoupled SaaS that is faster and easier to iterate.

AI-written summary · about

" chapters (8)

1. 0:00Decoupling introduction
2. 2:34Coupling and monolithic Drupal
3. 7:48Deploying decoupled apps
4. 12:44Advantages of decoupling
5. 18:41Reasons not to decouple
6. 21:28Progressive decoupling
7. 25:43Decoupling success stories
8. 28:54Closing and Q&A

" related talks

• 52mShould We Decouple?Tom Mount · DrupalCamp NJ 2023
• 52m"Decoupled Drupal: Implications, risks and changes from a business perspective"Michael Schmid · Drupal Europe 2018
• 01h 04mDecoupled Drupal across the stackPreston So · MidCamp 2018
• 57mProgressively Decoupled Drupal, for everyone!Bryan Ollendyke, Michael Potter, Rebecca Goodman, Chuck Lavera · DrupalCamp NJ 2020
• 19mHarnessing Microfrontends: Platforms for Web AppsVenkata Sai Manoj Pasupuleti · Conf42 Platform Engineering 2024
• 39mAdventures in APIsSally Young · DrupalCamp Spain 2017
• 31mDecoupled, Not Disconnected: State and Sync in Micro-FrontendsAmira Shawky · reactjsday 2025
• 01h 07mDecoupled Drupal and the Front EndPreston So · Frontend United 2016