liveBook · Manning

Chapter 1: Microservices: an architecture for fast flow

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

The introduction frames faster, more reliable, lower-risk software delivery as the reason to consider microservices, while stressing that they are appropriate only for some applications.

After this chapter you will be able to

Section by section

Introduction

The introduction frames faster, more reliable, lower-risk software delivery as the reason to consider microservices, while stressing that they are appropriate only for some applications.

Key terms: microservice architecture, software delivery, fast flow

1.1 The need for fast flow

Defines fast flow and explains why business agility and dependence on software require smaller, more frequent releases with rapid feedback.

Key terms: fast flow, small changes, feedback

1.1.1 The software delivery feedback loop

This section explains the software delivery feedback loop and why frequent releases are needed to learn from users and validate technical decisions.

Key terms: feedback loop, production, release, fast feedback, volatile, uncertain, complex and ambiguous (VUCA), experiment, technology landscape, design decisions

1.1.2 Fast flow: continuous change and feedback

This section defines fast flow, shows how DORA metrics quantify software delivery performance, and explains its reported links to reliability, developer experience, and business success.

Key terms: fast flow, feedback, experiments, DORA metrics, lead time, deployment frequency, change failure rate, failed deployment recovery time, elite performers, smaller changes

1.1.3 The fast flow success triangle = DevOps + Team Topologies + Architecture

The section explains how DevOps, Team Topologies, and enabling architecture work together to support fast flow.

Key terms: fast flow success triangle, DevOps, Team Topologies, architecture, three ways, first way, second way, third way, reduce batch sizes, continuous delivery

1.2 Architectural requirements for fast flow

The section explains that architecture supports fast flow by enabling DevOps and Team Topologies, then previews the architectural requirements discussed next.

Key terms: fast flow, DevOps, Team Topologies, architecture

1.2.1 Architectural requirements for fast flow

The section explains why fast flow depends on architecture that lets teams change their code independently and move those changes rapidly through deployment.

Key terms: architecture, engineering organization, fast flow, loose design-time coupling, team autonomy, stream-aligned team, automated deployment pipeline, feedback loop, push, merge

1.2.2 The Monolithic architecture can enable fast flow

A monolith can enable fast flow, but growth can make cross-team changes harder and turn its shared deployment pipeline into a bottleneck.

Key terms: monolithic application, single codebase, single deployable unit, single deployment pipeline, fast flow, team autonomy, loosely design-time coupled, breaking changes, deployment pipeline, reduce batch sizes

1.3 A brief introduction to the microservice architecture

This section explains why a large application and organization may outgrow a monolithic architecture as a way to achieve fast flow.

Key terms: monolithic architecture, fast flow, deployment pipeline, microservice architecture

1.3.1 The microservice architecture: a definition

Defines the microservice architecture through its service structure, loose design-time coupling, and independent deployability, while correcting the idea that it requires many tiny services.

Key terms: architectural style, microservice architecture, service, deployable unit, business capabilities, subdomains, distributed architecture, lots of little services, tangible problem, excessive complexity

1.3.2 The microservice architecture is a fast flow architecture

This section explains how loosely coupled services and fast, dedicated deployment pipelines enable fast flow in large, complex applications.

Key terms: team autonomy, loosely design-time coupled services, technology stack, separate code base, dedicated deployment pipeline, lead time, processing time, utilization, feedback

1.3.3 Other benefits of the microservice architecture

This section explains how microservices support multiple technology stacks and allow modules with different characteristics to be deployed separately.

Key terms: multiple technology stacks, services, incrementally upgrade, application modules, separate services, high availability infrastructure, architectural properties

1.3.4 No such thing as a silver bullet: the drawbacks of microservices

This section explains why microservices are not a silver bullet: distributed operations, service coupling, design discipline, organizational practices, and deployment habits can all undermine their benefits.

Key terms: distributed operations, process boundaries, transaction boundaries, runtime coupling, eventual consistency, distributed monolith, design-time coupled, breaking change, service boundaries, loosely design-time coupled

1.4 When to use the microservice architecture

This section explains why choosing between a monolith and microservices depends on the application, whether it is new or already a monolith.

Key terms: monolithic architecture, microservice architecture, requirements, benefits, drawbacks, brand-new application, monolithic application

1.4.1 Building an application from scratch: typically a monolith-first approach

Recommends starting a new application as a monolith in most cases, while explaining when microservices may be justified and why starting with them can be risky.

Key terms: distributed monolith, stable APIs, loosely design-time coupled, boundaries, monolith-first approach, mixture of technologies, simple microservice architecture, segregating modules

1.4.2 Refactoring a monolith to the microservice architecture

This section explains how to decide whether a slowing monolith needs microservices and, if it does, why to migrate incrementally rather than rewrite it all at once.

Key terms: fast flow, monolithic architecture, DevOps, Team Topologies, automated deployment pipeline, loosely design-time coupled modules, big bang rewrite, Strangler Fig pattern, incrementally migrates

1.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 →

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.