Fundamentals of Software Architecture
Architecture as a discipline rather than an interview topic, covering architecture characteristics, styles, trade off analysis and the human side of the role. The book to read when you are moving from writing services to deciding how they fit together.
Book
System Design
Mark Richards and Neal Ford
6 to 8 weeks
Intermediate
About $50
What it is
A broad treatment of software architecture covering how to identify the characteristics that matter for a system, the major architectural styles and what each optimises for, decomposition, governance, documentation and the soft skills the role demands.
The idea worth taking
That architecture is the business of trade offs, and that the honest answer to almost every architectural question begins with it depends, followed by the specific factors it depends on. The book teaches you to enumerate those factors rather than to memorise a preferred style.
Where it complements interview material
Interview preparation teaches you to design a system under a clock. This teaches you to be responsible for one for three years, including the parts about communicating decisions and living with them.
Best for: senior engineers moving toward architecture, technical leads, and anyone whose design decisions now outlive their attention.
Ready to start?
Opens on Mark Richards and Neal Ford in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Every session is free; a few slots open each week.
Follow along
New writing, resources and project ideas land here first.