Pragmatic Architecture
summary
Argues architecture is simply a set of answers developers ask daily and shows how that plays out: picks concrete types (infrastructure, enterprise, solution), lists six architectural concerns (communication, presentation, state, processing, resources, tools), and evaluates tech choices with examples—Kotlin, Docker, Kubernetes, AWS, REST vs CORBA, Maven—using real cases (a crop‑insurance app for ~250 reps, a prototype that became production opening 47 DB connections). Provides a proto‑catalog to choose patterns that actually fit the problem.
AI-written summary · about
chapters (9)
- 0:00Introduction and humor
- 3:53What is software architecture
- 11:17Architecture astronauts and abstractions
- 25:20Defining architecture and style
- 39:33What is an architect
- 54:24Constraints and time in architecture
- 1:00:02Architecture as a conductor
- 1:07:24Proto-catalog of architecture elements
- 1:12:40Conclusion and Q&A
related talks
37mArchitecting for Tomorrow: A Pragmatic Perspective
46mPractical (a.k.a. Actually Useful) Architecture
54mArchitecture Is Not Nonsense
52mEvolving a Pragmatic, Clean Architecture A Craftsman's Guide
01h 00mPatterns for Software Architecture
01h 00mAgile Architecture
58mThe past, present and future of Architecture
38mAgile Architecture