Panel Discussion: Architecture
summary
The panel argues for hiring software architects early and having them fluent in code and business trade-offs; one company described an architect training roadmap with assessments and mentorship. Concrete microservice guidance: start with a monolith and only split into microservices when justified, because support and development costs can multiply — an invoicing microservice prototype took four months versus hours in a monolith. They also endorse continuous architectural retrospectives and incremental rollouts.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:50Architect's role
- 7:10Architect in product company
- 12:47When to involve architect
- 14:10Becoming an architect
- 19:47Microservices myths
- 33:25Microservice design mistakes
- 41:52Conclusion & Q&A
related talks
24mThe too many faces of Architecture
50mTowards an Evolutionary Architecture
18mSoftware Architecture Building Better Applications with Architecture Best Practices
41mArchitecture and Agility: A Shared Skillset!
45mSoftware Architecture for Humans!
01h 00mPanel
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
33mSet Design: Putting the "Art" in "Architecture"