Composability: The New Architect in Town
summary
A demo site for dogs with shopping, courses, videos and social features exposes failures of static pages and a monolith: content updates need engineering, images and product data diverge, and four APIs (CMS, DAM, PIM, ECM) slow development. The solution uses Contentful as a headless CMS within a composable stack built on microservices, adding modular components and orchestration so one API surfaces unified content, lets teams scale or swap parts independently, reuse assets, and ship features faster.
AI-written summary · about
chapters (12)
- 0:00Welcome
- 2:07About speaker and Contentful
- 4:40Building an ambitious website for dogs
- 7:05Static sites and CMS limits
- 9:11Headless CMS challenges
- 10:55Multiple platforms and APIs
- 11:39Monolithic architecture explained
- 13:43Microservices as building blocks
- 14:45Composability beyond microservices
- 16:50Orchestration and consistent user experience
- 17:53Composable architecture benefits
- 19:58Recap and conclusion
related talks
18mComposability: The New Architect in Town
26mFight the glue code monster and build painless websites and apps
24mAgility through Composable Architecture
18mFull Stack Composable Architecture
43mBeyond micro-services, embrace composable architectures
21mCreating a Culture of Innovation
22mHeadless architecture and the future of websites
51mContent is King: How Contentful and CaaS are Changing