liveBook · Manning

Software architecture

As explained in Microservices Patterns, Second Edition

The structures of a software system, including its elements, their relationships, and their properties.

Software architecture is the set of structures needed to reason about a system: its software elements, their relationships, and the properties of both. Decomposition shapes how people divide work and how elements interact to produce runtime behavior. section 3.1.2

Architecture must meet both user-facing needs, such as scalability and availability, and engineering needs, such as the ability to change and deploy software. A design that supports autonomous teams and rapid delivery requires loose design-time coupling and a fast, automated deployment pipeline. section 1.2.1 section 3.1.3

Five quality attributes help assess an architecture for fast flow:

  • Modifiability: make changes easily through loose design-time coupling and cohesion. section 5.7
  • Evolvability: upgrade the technology stack incrementally; for large applications, multiple components can allow decisions to be made separately. section 5.7
  • Testability: verify changes quickly through modularity, loose coupling, and deterministic behavior. section 5.7
  • Deployability: support fast, reliable, automated deployments and automatic rollback when problems occur. section 5.7
  • Observability: understand application and user behavior to support safe deployments and production feedback. section 5.7

A layered design decision

A layered architecture can define web/API, domain, and infrastructure layers, with rules that every element belongs to a layer and each layer depends only on the one immediately below it. Record the problem, candidate solutions, trade-offs, choice, and rationale so that each element can be traced to a need rather than added speculatively. section 3.4.1

Architectural styles constrain a system’s design. A monolith can enable fast flow for some applications and obstruct it for others; component architecture also affects how well large applications satisfy delivery and observability requirements. Choose the style against the requirements rather than treating microservices as an automatic improvement. section 1.2 section 3.0 section 5.7

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines architecture, examines quality attributes, and details design decisions, constraints, and their rationale.
Examples
Illustrates layered architecture with dependency rules and availability with a failed service instance.
What you can do after
Evaluate architectural choices against delivery needs, quality attributes, and the problems each decision solves.
How it connects
Connects architecture to DevOps, Team Topologies, quality attributes, and architectural styles.

Also explained in

Compare how 2 books explain software architecture →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.