Should We Decouple?
summary
Compares concrete architectures: partially/progressively decoupled (Drupal sends HTML skeleton, JS fetches pieces) versus fully decoupled/headless (React/Next, Vue/Nuxt, SvelteKit, SolidStart consume JSON API). Gives real outcomes: e‑commerce often wins, marketing sites sometimes get slower, Kingfisher’s decoupled stack performs well for two years then degrades, one client builds an API Gateway + GraphQL to smooth messy CMS JSON, security needs WAF and bot mitigation, staffing often requires hiring/front‑end augmentation, and rolling incremental POCs reduces risk.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:06What are we going to cover?
- 8:21Contextualizing the last few definitions
- 13:58Business Concerns
- 25:29Team Concerns
- 32:08Technology Ecosystem
related talks
52m"Decoupled Drupal: Implications, risks and changes from a business perspective"
29mDecoupling 101
30mThe Time for Decoupled Drupal is Now
31mDecoupled, Not Disconnected: State and Sync in Micro-Frontends
01h 04mDecoupled Drupal across the stack
22mHeadless architecture and the future of websites
01h 07mDecoupled Drupal and the Front End
57mProgressively Decoupled Drupal, for everyone!