[Summary] – Fundamentals of Software Architecture An Engineering Approach – Part 2: Laws of Software Architecture

This is my learning note from the book Fundamentals of Software Architecture: An Engineering Approach written by Mark Richards and Neal Ford. All the contents are mostly distilled and copied from the book. I recommend you to buy this book to support the authors.

Một số định luật kinh điển về Software Architecture chúng ta cần nằm lòng

Phần trước:

Part 1: Expectations of an Architect

Định luật SỐ 1

Everything in software architecture is a trade-off.

– First Law of Software Architecture

If an architect thinks they have discovered something that isn’t a trade-off, more likely they just haven’t identified the trade-off yet.

– Corollary 1

Định luật SỐ 2

Why is more important than how.

– Second Law of Software Architecture

The authors discovered the importance of this perspective when we tried keeping the results of exercises done by students during workshop as they crafted architecture solutions. Because the exercises were timed, the only artifacts we kept were the diagrams representing the topology. In other words, we captured how they solved the problem but not why the team made particular choices. An architect can look at an existing system they have no knowledge of and ascertain how the structure of the architecture works, but will struggle explaining why certain choices were made versus others.

Chúng ta sẽ học các kỹ thuật để nắm bắt các quyết định quan trọng trong “Architecture Decision Records”, từ đó đưa ra các quyết định kiến trúc cùng với các trade-offs tương ứng.