“Good Enough” Architecture Part 1
summary
Company builds a customization platform that requires downloading a 1GB Eclipse IDE and consumes dozens of person‑years, yet neither small nor large clients use it; a different project slices a system into tiny microservices across 200–300 developers and creates an entity‑centric order service that constantly causes overlapping changes and meetings; another project splits teams into front end and back end around a JSON API for a 10–20 developer product and sees blockers, secret full‑stack workarounds, and slowed delivery.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:32First statement about architecture
- 1:33Second statement about architecture
- 2:05Third statement about architecture
- 2:34Architecture antipatterns
- 3:33Cases
- 4:52Case No. 1: Non-extensible Extensibility
- 11:49Case No. 2: Perilously fine granularity
- 20:30Case No. 3: Horizontal Conway split
- 27:45Takeaways
related talks
33mFrom Enterprise Architecture to Software Design - Critical Thinking
05mDesign and Architecture: Special Dumpster Fire Unit
39mMinimal Viable Architecture
42mLarge-Scale Architecture: The Unreasonable Effectiveness of Simplicity
01h 29mMonolithic Delivery
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
49mCase study of a good enough architecture
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions