Drupal as the head in headless commerce
summary
Argues Drupal works best as the head when it ingests a remote commerce platform into Drupal Commerce and runs a full commerce integration (products imported with message queues, cart/checkout handled via transactional API calls). Recommends patterns: import for static product data, lazy load or on‑demand for users/orders, transactional pricing/carts, and strict respect data ownership. Practical tips: build a connection health checker, always log API failures, enable production debugging without deployments, and plan cache invalidation — caching proves the hardest operational problem.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:55Why Drupal as the head
- 6:39Architecture considerations
- 12:27Implementation tip one
- 17:34Data ownership and teams
- 18:21Possible architectures
- 23:22Integration approaches
- 27:24Log everything
- 31:28Debug on production
- 37:15Lazy load and on demand
- 43:38Product detail page example
- 48:44Q&A
related talks
07mAccelerating Composable Commerce with Strapi
24mArchitecting a Seamless E-commerce Platform Transition
22mOptimization strategies for a performant, headless storefront
30mExtend AEM Content & Commerce with Adobe Developer App Builder
50mMaking Drupal Less Daunting
12mMaking commerce. Faster.
29mAdopting a Drupal Contrib-First Approach
56mHow to keep Drupal relevant in the Git-based and API-driven CMS era