liveBook · Manning

Chapter 11: Architectures that flow

What you will learn in chapter 11 of Build High Value Software Systems

The introduction shows why architecture must be examined as a value stream, even when code and development processes are working well.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction shows why architecture must be examined as a value stream, even when code and development processes are working well.

Key terms: architecture, value stream, queues, bottlenecks, overproduction, architectural waste, constraint, synchronous microservices, bottleneck

11.1 Set-based design

This section explains how short, parallel architecture spikes help teams make consequential design choices using evidence rather than early guesses.

Key terms: set-based design, spikes, throwaway prototypes, go see, genchi genbutsu, candidate set, evaluation questions, operational constraints, throughput, latency

11.2 The last responsible moment

The section applies Just in Time thinking to architecture and defines when an architectural decision can no longer be delayed.

Key terms: Just in Time (JIT), inventory, architectural decisions, last responsible moment, important option

11.2.1 Decisions that can wait

This section explains how to defer architectural decisions until code, data, or contracts are about to depend on them, using the monolith-versus-microservices choice as an example.

Key terms: trigger point, last responsible moment, monolith versus microservices, real traffic patterns

11.2.2 Decisions that cannot wait

The section explains why foundational architecture decisions sometimes need to be made immediately, then revisited as the system and its value stream change.

Key terms: JIT, inventory cost, authentication and authorization model, logging and observability standards, standard work, kaizen cycle, architectural debt, value stream, shared contract, incompatible contracts

11.2.3 Tracking decisions

This section shows how an architectural decision log makes deferred decisions actionable and preserves the context needed to revisit decisions when conditions change.

Key terms: architectural decision log, trigger, deferred, last responsible moment, constraints at the time, root cause analysis, kaizen cycle, superseded

11.3 Value stream mapping at the system level

This section shows how to map a request across an entire architecture to expose hidden wait time, redesign unnecessary blocking, and track architectural flow over time.

Key terms: system-level value stream mapping, activity ratio, hidden latency, synchronous chain, parallel, asynchronously, user-visible latency, distributed tracing, queue time, processing time

11.4 Finding the system bottleneck

This section applies the Theory of Constraints to architecture by locating a shared-resource bottleneck and improving system flow through five focusing steps.

Key terms: Theory of Constraints (ToC), constraint, shared PostgreSQL database, identify, exploit, subordinate, elevate, repeat, flow, system throughput

11.5 Pull versus push

This section contrasts synchronous push architectures with queue-based pull architectures and explains how pull keeps work moving when downstream services are slow or unavailable.

Key terms: push, temporal coupling, cascading failures, scaling is coupled, Lean principles, overproduction, backpressure, defect propagating, pull architecture, queue

11.5.1 Backpressure: The safety valve

This section explains how backpressure makes service capacity visible and helps teams choose where to use pull-based queues alongside synchronous calls.

Key terms: backpressure, bounded queue, producer, consumer, pressure, headroom, bottleneck, push, pull, kanban

11.6 Takt time and system rhythm

The section explains how takt time measures the pace required by customer demand and how drum-buffer-rope coordinates a software system around its constraint.

Key terms: takt time, customer demand, system rhythm, drum-buffer-rope, constraint, buffer, rope, queues, backpressure

11.6.1 Calculating takt time

The section calculates takt time from customer demand and uses it to assess capacity, monitor headroom, and find pipeline bottlenecks.

Key terms: takt time, available time window, customer demand, processing time, concurrent processing pipelines, headroom factor, actual throughput, current demand, andon signal, yellow signal

11.7 Building quality in

The section shows how to protect system flow by stopping defects at their source and avoiding architecture that exceeds demonstrated needs.

Key terms: jidoka, andon, circuit breaker, open state, poison message, dead letter queue (DLQ), transient failures, input validation, andon signal, overproduction in architecture

11.8 A system that flows

The section connects the chapter’s architectural practices into a repeatable approach to keeping a system flowing as it changes.

Key terms: set-based design, last responsible moment, value stream mapping, Theory of Constraints, takt time, pull systems, value streams, constraint, kaizen

11.9 Exercise: Mapping, measuring, and improving your architecture

This exercise asks readers to map a critical request path, audit architectural overproduction, design service health responses, and assess the path’s drum-buffer-rope and rhythm.

Key terms: value stream, queue/wait time, processing time, network time, activity ratio, constraint, overproduction, average daily traffic volume, API endpoint, configuration parameters

11.10 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 10: Kaizen: Continuous improvement Chapter 12: Lean operations and production →

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.