Books for Great Software Architects
It has been common to see posts and articles talking about what a software architect must read and what your book library, as an architect, should include. However, no one explains how to read them or if there is a specific sequence you must follow.
Personally, and through my reading journey, I found a link between these books. This link defines which book is considered a pre-requisite for another and which book’s content can make sense when read after another and which one should be the next to gain the full picture.
Without knowing this link, the reading will be rough and frustrating, consuming a lot of your time and effort. For example, and in many cases, I had to read the same book twice; the first time was before reading its pre-requisites, which was boring and confusing. On the second time, it was after reading the right pre-requisites, where everything suddenly became crystal clear.
In this article, I will show and explain the right reading sequence for the most important books in the software architecture world in the form of a roadmap composed of multiple paths, which is supposed, if followed, to streamline your reading process and make your journey smoother (hopefully smoother than mine) and to become a great software architect faster.
Note: In this article, it’s assumed that you have a good experience in one or more programming languages and you are interested in entering the software architecture world.
As explained in my previous article “Types of Technology Architectures”, there are many different types of software architectures that address different types of specializations, such as Application Architecture, Integration Architecture, Data Architecture, etc.
The reading roadmap in this article follows the same and it will have different paths according to the different types of software architectures, as depicted below:
As per the roadmap, no matter which architecture type you are interested to be specialized with, there is a fundamental path that must be followed before going into your own specialization.
Accordingly, the article is divided into 4 parts:
- Part 1 covers Fundamentals Path
- Part 2 covers Application Architecture Path
- Part 3 covers Integration Architecture Path
- Part 4 covers Data Architecture Path (still under progress)
Don’t forget to follow me to get notifications for my new articles and please clap for the article if you liked it.