Description

Leverage leadership knowledge to make better software architecture decisions. Think deeply but implement slowly.

The overarching goal of software systems (hence, for software architecture) is to build systems that meet quality standards and provide the highest return on investment (ROI) in the long run or within a defined period.

A great product requires a combination of technology, leadership, and product management (including UX). Leadership is primarily about managing uncertainty and making the right judgment. To build great products, technical leaders need to combine their knowledge of technology, leadership, and product management and make the right decisions. Many technical mistakes come from the gap between knowledge about these three items and judgment.

In Software Architecture and Decision-Making, Srinath Perera explains principles and concepts that software architects must understand deeply and how to employ those principles to manage uncertainty. The questions and principles discussed in this book help manage uncertainty while building software architecture and provide a decision-making framework. This book is for all technical leaders in the software industry who make holistic judgments about the systems they build and for future leaders learning the craft.

As software architects, we learn about abstractions, architectural styles, and patterns. We study their pros and cons, which one to use in a given situation, and how to compose them with an awareness of pitfalls, negative examples, and use cases. However, many errors are made not because we do not understand these things. Most design mistakes are caused by a lack of judgment, not by a lack of knowledge. Here, judgment refers to the ability to make considered decisions or arrive at sensible conclusions optimizing for the most important outcome.

Understand the importance of strong decision-making with examples from great technical leaders such as the Wright brothers and Kelly Johnson
Leverage five key questions and seven important principles to understand uncertainties during the design process and make strategic architectural decisions
Approach the design systematically, first at the macro level and then at the individual service level

This definitive guide explains principles and concepts–technical and non-technical alike–that software architects, senior software engineers, and technical leads must understand to manage the inevitable uncertainty involved in building software systems and drive the products’ success.