liveBook · Manning

Build view

As explained in Microservices Patterns, Second Edition

An architectural view describing source repositories, build projects, and the path changes take from development to production.

The build view describes how code moves from a developer’s laptop to production. As a static architectural view, it focuses on repositories, build projects, and deployment pipelines. section 3.2.4 section 3.5

Trace the path through three elements:

  • Git repositories hold subdomain code and infrastructure configuration. section 3.2.4
  • Build projects within repositories build and test components. section 3.2.4
  • Pipelines, usually triggered by a Git push or another pipeline’s completion, build and test components, then deploy them to production after tests pass. section 3.2.4

Fast pipelines provide quick developer feedback. Incremental builds reuse earlier results and rebuild only elements affected by a change; ephemeral cloud environments may need a build cache to preserve those results. section 3.2.4

Repository organization

A monolithic architecture may use one repository, build project, and pipeline. A microservice architecture may use multiple repositories, each with its own project and pipeline. section 3.2.4

Figure 3.10 One of many ways of organizing code repositories, build projects and deployment pipelines is a single repository, build project and pipeline, as seen in monolithic architectures
monolith repo pipeline view

See the single-repository, single-project, single-pipeline organization. section 3.2.4

Figure 3.11 Another way of organizing code repositories, build projects and deployment pipelines is multiple repositories, and one build project and one pipeline per repository, as seen in microservice architectures.
microservice repo pipeline view

See the multiple-repository organization with a project and pipeline per repository. section 3.2.4

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines repositories, build projects, and pipelines, then explains triggers, test-gated deployment, and incremental-build caching.
Examples
Compares a monolith’s single repository and pipeline with microservices’ per-repository projects and pipelines.
What you can do after
Operate pipelines that build, test, and deploy components, and speed them with incremental builds and caches.
How it connects
Connects repositories to subdomains and infrastructure configuration, and pipelines to build tools and deployment.

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.