Adventures in APIs
summary
Argues that Drupal can be decoupled into practical, production systems and shows concrete projects: a 2012 live sports JS frontend, partially decoupled MSNBC, Hotwire prototype, and a fully decoupled lot.com using transformed nodes stored in couchDB/pouchdb documents. Recommends Drupal 8 REST and JSON:API (and mentions GraphQL), warns about many-request pitfalls, monster endpoints, HTTP/2 rendering jumps, routing/redirect complexity, auth headaches, and demonstrates working live preview and tooling like Waterwheel and Matteo’s modules.
AI-written summary · about
chapters (16)
- 0:00Welcome and introduction
- 1:53What is decoupling?
- 3:15Real-world decoupled projects
- 6:55Tools for decoupling in Drupal
- 9:02Challenges of custom endpoints
- 12:15HTTP/2 and performance issues
- 13:38JSON API and GraphQL solutions
- 16:50API distributions and document databases
- 18:58WordPress and other CMS competitors
- 22:54Drupal’s API advantages
- 23:37Proprietary CMS comparison
- 24:20Live demo of live preview
- 25:55What’s difficult when decoupling
- 27:20Routing in decoupled apps
- 31:12Internally decoupling Drupal
- 32:36Q&A and closing remarks
related talks
52m"Decoupled Drupal: Implications, risks and changes from a business perspective"
59mHeadless Drupal
01h 04mDecoupled Drupal across the stack
54mDecoupling Patterns, Services and creating an enterprise level editorial experience
51m"Decentralized Drupal: The decoupled Drupal endgame"
30mThe Time for Decoupled Drupal is Now
57mProgressively Decoupled Drupal, for everyone!
52mShould We Decouple?