Breaking Down Your Build: Architectural Patterns For A More Efficient Pipeline
summary
Argues that the fastest build is the one you don’t need to run and gives five concrete patterns to prove it: decouple API from implementation, slice by domain instead of by tier, turn shared libraries into services, split giant utils into independent modules, and externalize configuration. Shows migration steps (create empty jobs, explicit wiring, duplicate namespaces), uses Maven/TeamCity/Artifactory examples, and reports cutbacks like rebuilding 4 modules instead of 7 and avoiding hour‑long cascades by converting build‑time deps to runtime calls.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 2:09Continuous Integration and Continuous Deployment
- 4:09Complexity vs Simplicity
- 9:00Monolith Architecture
- 10:27Microservices Architecture
- 12:50Make a change
- 13:25Refactor skills
- 14:36Safety
- 16:33Patterns
- 16:59Avoid Build phases
- 18:24Identifying and restoring sub builds
- 19:40Transforming built dependencies into dependencies
- 20:16Coupling API from implementation
- 26:08Slicing
- 31:41Library
- 36:44Fan Out
- 41:43Configuration
- 51:44Reflection
related talks
41mPipeline Patterns and Antipatterns - Things your Pipeline Should (Not) Do
30mEverything is an API
45mLess is more—a build pipeline for the modern age
35mEverything is an API
43mBuilding for Developers
41mUsing Boundary-Driven Development to beat code complexity
42mPatterns that pay off
01h 29mArchitecture Beyond Clean & Hexagonal