liveBook · Manning

Software architect

As explained in Grokking Software Architecture

A person responsible for guiding the structural and system-wide design of software.

A software architect is not necessarily a distant decision-maker with a whiteboard. Choosing where logic belongs, how to structure a class, or how to query a database already involves architectural decisions. The role is about making those choices deliberately, not holding a special title. section 1.1

There is no perfect design without downsides. Architectural choices cost time, money, team energy, customer happiness, or future flexibility; shortcuts also create technical debt. The practical goal is to choose tradeoffs the team can live with and explain why. section 2.2

Make architectural choices defensible:

  • Identify the constraints and likely costs of each option. section 2.2
  • Choose the downsides the team can accept now, rather than chasing a design with no weaknesses. section 2.2
  • Track results with measures such as maintenance time, bug rates, onboarding time, incidents, or feature delivery time. section 2.2
Figure 2.1 Archie sees the mirage of perfect architecture in the distance. He desperately tries to crawl towards it, not realizing it’s a figment of his imagination.

The mirage of a perfect architecture captures the trap: chasing an ideal design can keep a team refactoring instead of shipping. section 2.2

How Grokking Software Architecture covers it

How deep it goes
Defines the role and explains tradeoffs and success metrics, while stopping short of detailing a full decision-recording process.
Examples
Uses logic placement, class structure, and database queries alongside incident and feature-delivery metrics.
What it assumes
Assumes no formal architecture background and reframes ordinary coding choices as architectural decisions.
What you can do after
Evaluate tradeoffs, choose acceptable downsides, and defend decisions with measurable results.
How it connects
Connects software architecture with system design, technical debt, constraints, and measurable outcomes.

Also explained in

Compare how 3 books explain software architect →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.