Software Architecture

"The architecture is the single largest influence on the design and future growth of a software system. It is therefore essential to get it right in the early stages of development." - Pete Goodlife.

I will give my opinion about the chapter 14 of the “Code Craft: The Practice of Writing Excellent Code" book by Pete Goodlife.

This chapter takes in mind about the definition of software architecture and shows the qualities of a good architecture, in the text has some examples of what a bad architecture looks like, as the chapter said, if you don't take a holistic vision when you are making the design, then the result will be an awful design that it can work but it will be really hard to understand.

Good system architecture is simple. It can be described in a single paragraph and summarized in one elegant diagram." - Pete Goodlife.

I agree with the author and I summarize in the following lines what an architecture needs to be according to the ideas of the author:

An architecture needs to be simple.

A simple architecture refers to the fact that a system should not have too few or too many components. The important fact is that the architecture needs to have the necessary methods to get to the goal because, in the end, that is the real important point to consider.

An architecture needs to be comprehensible.

A comprehensible architecture means that the functionality can be represented visually without major problems. Having the diagram in a high-level vision (not having details about the tech implementation) is good because an architect needs to understand and remember the system fast in order to have a holistic vision.