liveBook · Manning

Chapter 3: Software architecture: what is it, why does it matter and who does it?

What you will learn in chapter 3 of Microservices Patterns, Second Edition

The introduction argues that understanding architecture fundamentals is necessary before deciding when and how to use microservices, then previews the chapter’s topics.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction argues that understanding architecture fundamentals is necessary before deciding when and how to use microservices, then previews the chapter’s topics.

Key terms: software architecture, architecture fundamentals, microservice architecture, FTGO organization

3.1 What is software architecture and why does it matter?

Introduces the questions of what software architecture is and why it matters, before turning to an outside view of an application.

3.1.1 An application as a black box

This section describes an application from the outside, in terms of the system operations it exposes and the events it publishes.

Key terms: black box, system operation, command, query, event, REST API, messaging technology, passing of time, system command, OrderCreated

3.1.2 Software architecture: a way to reason about your application

The section defines software architecture as a way to reason about an application's parts and relationships, then explains why that decomposition matters.

Key terms: software architecture, software elements, relations, decomposition, division of labor and knowledge, runtime behavior

3.1.3 Why architecture matters

The section explains why architecture matters by comparing three ways to describe the requirements it satisfies and showing how quality attribute scenarios make those requirements testable.

Key terms: architecture, quality attribute, functional requirements, non-functional requirements, runtime behavior, development-time requirements, architecturally significant requirements, quality attribute scenario, stimulus, stimulus source

3.2 Software architecture is multidimensional

The section introduces view models for describing an application’s architecture and presents the author’s four static views plus a scenario view.

Key terms: N+1 view model, static view, elements and relations, scenario view, domain view, component view, deployment view, build view, subdomains, components

3.2.1 Domain view

The section explains how the domain view organizes an application into business-focused subdomains, how those subdomains collaborate, and how their business logic connects to the outside through adapters.

Key terms: domain view, subdomain, packages, Whole-Part relationships, system operation, uses relationship, createOrder(), Order Management, Consumer Management, Delivery Management

3.2.2 Component view

The section explains how the component view groups subdomains into executable or deployable units and shows how those units collaborate.

Key terms: component view, subdomain, component, executable or deployable unit, component architecture, Whole-Part relationship, system operations, collaboration, API, uses relationship

3.2.3 Deployment view

This section explains how the deployment view maps application components onto infrastructure and how deployment choices reflect an application’s quality needs.

Key terms: deployment view, component instances, infrastructure elements, networking resources, infrastructure code, desired state, Terraform, CloudFormation, Kubernetes YAML manifests, system quality attributes

3.2.4 Build view

This section explains how the build view traces code from a developer’s laptop to production and how build and pipeline structure affects feedback speed.

Key terms: Build view, Git repositories, build projects, deployment pipelines, incremental builds, build cache, ephemeral environments, fast feedback, monolithic architecture, microservice architecture

3.2.5 +1 Scenarios

Scenarios add behavior to the four structural architecture views by showing how elements collaborate to meet requirements or how changes reach production.

Key terms: scenarios, domain view, component view, deployment view, build view, system operation, user story scenario, architecturally significant scenarios, classes, subdomains

3.3 Overview of architectural styles

Defines an architectural style as a constrained set of components and connectors for describing a view of an application, and notes that applications typically combine styles.

Key terms: architectural style, components, connectors, view, constraints

3.3.1 Layered architecture

This section defines layered architecture, illustrates it with three-tier architecture, and explains where its depiction of an application’s dependencies falls short.

Key terms: layered architecture, strict layering, dependencies, three-tier architecture, domain view, presentation layer, business logic layer, persistence layer, repository interfaces, DAO classes

3.3.2 About the hexagonal architecture style

This section explains how hexagonal architecture organizes business logic, ports, and adapters, and why that organization is useful.

Key terms: hexagonal architecture, logical view, business logic, adapters, layered architectural style, port, inbound port, outbound port, inbound adapter, outbound adapter

3.4 Architecting: what is it, who does it and when?

The section distinguishes an application’s architecture from the process of architecting that creates it.

Key terms: architecture, artifact, architecting

3.4.1 Architecture as a series of design decisions

The section presents software architecture as the cumulative result of explicit design decisions and explains what those decisions contain and why recording them is useful.

Key terms: architecture, architecting, design decisions, problem, motivation, cause, candidate solutions, trade-offs, decision, design decision

3.4.2 Who defines an application’s architecture?

This section compares who can make architectural decisions, explains why team-level decisions need an advice process, and distinguishes service-level from application-wide architecture in microservices.

Key terms: benevolent dictator, centralized decision-making, buy-in, implicit architecture, big ball of mud, architect in the team, architecture done by team members, decentralizing architecture decision-making, architecture advice process, people impacted

3.4.3 When to architect?

Start with the simplest working architecture, evolve it as real needs arise, and anticipate future needs only when evidence supports doing so.

Key terms: Gall’s Law, simplest architecture that works, architectural design decisions, over-engineering, scalability, actual evidence, wishful thinking

3.5 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 2: FTGO: A case study in moving from one kind of development hell to another Chapter 4: The importance of loose coupling →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.