Decoupling Drupal Commerce to Multiply and Scale the Front-end
summary
Centarro argues for an API-first Drupal Commerce stack and shows concrete tooling: Commerce API exposes cart, checkout, and resolved dynamic pricing for anonymous carts (on‑site payment token support is left for future work). Created modules include JSON API cross-bundles, JSON API resources, user resources and search API. A Matsmart migration progressively decouples (add-to-cart then full headless) and scales to Matsmart €10M and tens of thousands concurrent users; price lists target up to 15 million SKUs and 300k-item price lists. A Centarro Commerce distribution plus a React demo app exists.
AI-written summary · about
chapters (9)
- 0:00Why decouple e-commerce
- 1:43When to consider decoupling
- 3:56Omni-channel growth
- 5:28Scalability and performance
- 6:44Case study: Maxilla
- 9:01Multi-tenant architecture
- 10:42Tooling and custom modules
- 14:10Sentaro distribution overview
- 16:31Q&A and community resources
related talks
46mUsing Drupal Commerce for rich eCommerce experiences
34mContent driven eCommerce with Drupal Commerce
31mThe state of modern e-commerce
01h 04mDecoupled Drupal across the stack
17mMaintaining performance across a highly dynamic commerce site
07mHeadless vs Traditional eCommerce Platforms: Introducing Commerce Layer
12mMaking commerce. Faster.
36mHow to Build Content and Commerce Experiences Using App Builder and API Mesh