三津石智巳

👦🏻👦🏻👧🏻 Father of 3 | 🗺️ Service Reliability Engineering Manager at Rakuten Travel | 📚 Avid Reader | 👍 Wagashi | 👍 Caffe Latte | 👍 Owarai

Books I'm reading 📚 Software Architecture for Developers by Simon Brown


I was wondering what's the difference between architecture and design. This book has good insights for the question.

Essentially, Grady is saying that the significant decisions are “architecture”, and that everything else is “design”.

It's simple. 

The architectural decisions are those that you can’t reverse without some degree of effort. Or, put simply, they’re the things that you’d find hard to refactor in an afternoon.

Whether it's an architecture or design is determined by chnge cost.

As with many things in life, there is a sweet spot here awaiting discovery. The answer to how much is “enough” up front design and technical leadership will be explored throughout the rest of this book.

How much architecture is just enough?