Q&A session with Mark Richards
summary
Covers concrete claims and practical patterns: a new book on the hard parts of distributed systems, step‑by‑step component-based decomposition for migrating monoliths, why a modular monolith is a good startup default, Kafka for telemetry and high-throughput streaming, and serverless framed as a deployment strategy with cold‑start tradeoffs. Includes migration tradeoffs, examples of flattening namespaces, timelines (coding drops to ~20% for architects), and which approaches actually worked in real projects.
AI-written summary · about
chapters (26)
- 0:00Start
- 2:19What Are the Fundamental Skills and Key Attributes To Become an Architect
- 5:24Architectural Thinking
- 10:41What's the Difference between Architecture and Design
- 11:34Stretching Your Comfort Zone
- 12:02Key Skills
- 17:45Evolutionary Architecture
- 25:43The Modular Monolith
- 26:24Modular Monoliths
- 36:56What Is a Micro Front End
- 39:37Is There an Alignment between Vertical Markets and Architecture
- 44:57Examples of Use Cases for Event Driven
- 45:09Any Use Case for Servers
- 45:54What Is Microservices
- 46:07What Is Serverless
- 49:53Is There a Way for a Painless Transition from Monolithic Application to Microservices
- 50:13Helping Companies Migrate from Monolithic Applications to Microservices
- 52:00Paradigm Shift
- 52:39The Elephant Migration Anti-Pattern
- 58:45Tactical Forking
- 1:03:51Does Is Kafka Required in Microservices
- 1:11:07Principle of Least Astonishment
- 1:12:42First Law of Software Architecture
- 1:13:06Graphql
- 1:17:00Team Structure
- 1:25:37Thoughtworks Technology Radar
related talks
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
26mArchitecting for scale
01h 00mPanel
32mSplitting the monolith
01h 02mDistribu-ready with the Modular Monolith
44mAll the cool kids...
31mMonolith to Microservices: A Guide to Seamless Transitions
39mConsidering Migrating a Monolith to Microservices?