Architecting for rapid, frequent, reliable delivery of software.
summary
Argues that businesses need RFRS delivery and measures it with Accelerate metrics: lead time under an hour, deployment frequency many times a day (Amazon once reported ~130,000/day). Recommends monoliths for small teams and apps; advocates microservices for large, long-lived systems using per-service databases, independent deploys, and small teams (5–9). Explains runtime vs design-time coupling and solutions: sagas/choreography, CQRS/replicated reads, consumer-driven contract testing, and warns against shared schema or business-logic libraries.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:09What is software architecture?
- 9:53Why architecture matters
- 11:17Rapid frequent reliable delivery
- 24:41Monolithic vs microservices
- 32:29Microservice architecture
- 44:37Loosely coupled services
- 1:00:22Summary and Q&A
related talks
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
01h 00mAgile Architecture
01h 29mMonolithic Delivery
46mAgility and Architecture Together – Enabling a Fast Flow of Change
01h 26mChaos Development: Removing Software as the Inhibitor of Agile
12mSAG Expert Interview #08: Fast Flow for agile & safe software deployment
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
48mAgility and Architecture Together – Enabling a Fast Flow of Change