Agile Architecture
summary
Argues that architecture is the “important stuff” and shows concrete practices that make hard decisions reversible: database migrations (Liquibase, Rails migrations), consumer‑driven contracts for services, and small incremental refactors. Describes an Inception to agree what’s hard to change, using exemplars in code, regular commit reviews (triage + pairing), showcases with tools like Gatling, and a dependency‑analysis + wall diagram that enforces rules by failing the build if illegal dependencies reappear. Emphasizes carving time for senior devs to maintain coherence.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:21Agile and Architecture
- 1:41Definition of Architecture
- 6:14What Is Agile
- 10:20Responding To Change Over Having a Plan
- 12:19Architecture without Architects
- 14:58Inception
- 18:33Consumer-Driven Contracts
- 19:42Stories
- 24:00Gatling
- 25:18Collaboration
related talks
01h 00mAgile Architecture
41mArchitecture and Agility: A Shared Skillset!
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
51mWhy We Need Architects (and Architecture) on Agile Projects
37mArchitecting for Tomorrow: A Pragmatic Perspective
59mAgile Engineering: The Hard Parts
47mAgile and Architecture: a meeting of the undead
49mAgile and Architecture: a meeting of the undead