Composability: The New Architect in Town
summary
Argues that adopting composable architecture—built on microservices—lets teams bring product data from PIMs, DAMs and headless CMS into a single platform (Contentful) and publish via one API call, cutting redundancy and keeping legal and product copy consistent across channels. Components are independent and interoperable so teams work in parallel, services get swapped when better tools appear, and orchestration enables reusability and scalability, speeding delivery without breaking experiences.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:11Internet usage and content consumption
- 3:41About Contentful and myself
- 4:46Talk agenda overview
- 5:29History of content management systems
- 7:14Monolithic architecture explained
- 9:44Microservices and their benefits
- 11:54Composability explained
- 13:22Contentful's composable approach
- 15:29Advantages of composable architecture
- 17:36Recap and conclusion
related talks
20mComposability: The New Architect in Town
24mAgility through Composable Architecture
43mBeyond micro-services, embrace composable architectures
23mComposability is to Software as Compounding Interest is to Finance
56mCompositional UIs - the Microservices Last Mile
26mFight the glue code monster and build painless websites and apps
01h 02mCompositional UIs - the Microservices Last Mile
18mFull Stack Composable Architecture