Repository files navigation

A comprehensive list of books on Software Architecture.

People in the software industry have long argued about a definition of architecture. Ralph Johnson famously definedsoftware architecture as "the important stuff (whatever that is)." I, subjectively, followed his definition whiledeciding whether or not to include a specific book.

• What is this? (important)
• How did I make this?
• What should I read?
• Inclusion criteria
• Sorting criteria
• Books
  • System Architecture
  • Design Patterns
  • Domain-Driven Design
  • Microservices
  • Data Engineering
  • Streaming and Messaging
  • Distributed Systems
  • Cloud Engineering
  • Web Scalability
  • Agile
  • DevOps
  • General
• Find me at Goodreads

This is NOT a recommendation list. When I made this, I intended for a comprehensive list excluding low-profile books—seeinclusion criteria below. There was a simple reason behind that: I'm not a subject-matter expert on all these topics. Infact, I not a subject-matter expert on even a single topic of these. More importantly, I don't know your experiencelevel nor your preferences. Some people prefer theoretical over practical books (I do). Others prefer foundational overcomprehensive books or dry over engaging books or art-based over engineering-based books. Some people even enjoy verboseover concise books. Or and or and or.

I thoroughly reviewed all bookstagged with software-architecture on Goodreads and applieda simple algorithmic rules—see the inclusion criteria below. I don't think the list is perfectly comprehensive. Yet, I'mplanning to update it regularly to make it as comprehensive as possible.

Don't be overwhelmed by the number of books on each subject. Practically speaking, you are supposed to read a few bookson the subjects of your interest. Deciding what to read is your business. Personally, I start by reading a couple ofreviews on Goodreads and examine the book table of content, if available. When in doubt, I read more reviews over theinternet from blogs and the like. Alternatively, you may go with the Goodreads community preferences and start from thetop of each list if you don't have the time to read reviews.

• The book must be relevant to Software Architecture; and
• The content is not obsolete.
• It must be technology agnostic or applicable to a wide range of technologies; and
• The book profile on Goodreads matches these rules:
  • An average rating of 3.5 or above; and
  • A total number of ratings equals 50 or above.
  • At least 5 written reviews.
  • A minimum length of 50 pages.

The books are sorted solely based on the number ofwritten reviews. There are, however, other important factorsworth considering. For example, the average rating, the number of ratings, and the publishing date. Yet, I don't have anidea to put all these factors in a reasonable mathematical formula. If you haveany,I'd love to hear what you've got in mind.

This work is licensed underaCreative Commons Attribution 4.0 International License.