Component Symphony: Composable Components for Rapid Delivery
summary
Atlasian’s admin platform hosts 70 applications, so the team replaces brittle, hard-to-reuse UI with a three‑layer pattern: atomic stateless components, stateful capability components that remain contextless to parents, and pages that pass minimal contracts. A reusable validation capability for Cloud‑to‑Cloud Jira migrations handles huge orgs, calls services through a router/middleware and adapter layer to unify responses, and plugs into the Atlas hub design system. Result: lower duplication, smaller blast radius, faster delivery and measurable developer velocity gains.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:00Single Admin Platform
- 2:15Challenges
- 3:00Myth
- 3:52What went wrong
- 6:10Problem Statement
- 9:36Architecture
- 11:23Unified Approach
- 12:40Our Journey
- 14:10Outro
related talks
47mDeploying atomic design system at scale
21mShared Components Beyond the Design System
20mComposability: The New Architect in Town
24mAgility through Composable Architecture
39mRe-Compose your UI: building an atomic design library
18mComposability: The New Architect in Town
36mAngular, React, Vue and co: Harmoniously united by web components and micro apps?
44mComponents: Big, Small, or Do 'em All?