Architecture: The Stuff That's Hard to Change
summary
Argues that software architecture is literally architecture is the stuff that's hard to change: make decisions, communicate them, and enforce them. Recommends analysing systems by look at boundaries (traffic, protocols, caching, failure modes) rather than code, and verifying architecture by monitoring real traffic and dashboards not by consuming code reviews. Gives concrete rules: wait to generalize until three duplicated solutions exist (wait till you have three), prefer buying proven services (Mandrill/MailChimp, Dynamics CRM used successfully), and build monitoring to validate choices.
AI-written summary · about
chapters (7)
- 0:00Introduction to architecture
- 2:51Origin of engineering and architecture
- 10:36Architecture vs development
- 17:38Making architectural decisions
- 28:12Communicating architecture decisions
- 37:20Reinforcing architectural decisions
- 47:24Future of software architecture
related talks
45mArchitecture: The Stuff That's Hard to Change
49mWhy software architects fail: and what to do about it
46mTHE too MANY FACES OF ARCHITECTURE
51mSoftware Architecture for Humans!
37mSoftware Architecture for Humans!
45mSoftware Architecture for Humans!
38mAgile Architecture
25mThe (too) Many Faces of Architecture