Everyone architect!
summary
A company scaled from a 30-person monolith to ~300–500 engineers with hundreds of microservices and ML products and found a centralized architecture committee and later a full-time team became bottlenecks. They adopted written Architecture Decision Records (a 6-field Markdown template), synchronous cross-team reviews, a published decision portal, and enforced high-level architecture principles; the process requires options, trade-offs and uses consent (not consensus), which pushed architecture responsibility out to teams and allowed alignment to scale without central control.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:05Leboncoin’s architecture evolution
- 3:56Architecture committee limits
- 6:22Dedicated architecture team
- 8:49Collective architecture return
- 9:53ADR method for architecture
- 13:50Results and alignment principles
related talks
45mTowards Architecture Organization Topologies for Sustainable Fast Flow of Change
44mWhen your boss decides to have an architecture team…
47mMaking architecture decisions, the Agile Way
44mArchitectural Practices for Greater Scalability and Innovation
23mScaling engineering teams with an architecture North Star
29mUsing architecture groups to scale people and technology
58mRefactoring the Architect’s role
45mArchitecture and the Architect AD2022