Gradle serves as a concrete build-tool example for build-time coupling: dependencies among subprojects affect how much must be recompiled and retested after a change. Ideally, only changed subprojects need this work; coupling can expand it to the entire component and delay feedback. section 4.3 section 4.3
Gradle
An open-source build automation system that models builds as tasks and supports dependency management and incremental execution.
How Microservices Patterns, Second Edition covers it
- How deep it goes
- Explains how coupling changes recompilation and retesting scope, from changed subprojects to an entire component.
- Examples
- Contrasts rebuilding only changed subprojects with rebuilding and retesting the entire component.
- What you can do after
- Evaluate how build-time coupling expands recompilation and retesting after a change.
- How it connects
- Connects Gradle to build-time coupling, subprojects, recompilation, retesting, and developer feedback.
Also explained in
-
Fast by DefaultGradle is a build automation system with a programmable model for compiling, testing, packaging, and resolving dependencies.
-
Developer Experience on KubernetesGradle is a build automation tool for defining and executing software build workflows, including dependency management and testing.
-
Kafka Streams in Action, Second EditionGradle is a build automation tool that defines and executes project tasks, dependency management, and source-generation workflows.
Compare how 4 books explain Gradle →
Related concepts
- Mavenalternative to · Apache Maven is a build automation and project management tool that manages dependencies and build lifecycles, especially for Java and other JVM projects.
- build systemkind of · A build system is software that automates transforming source code and project inputs into artifacts through tasks such as compiling, testing, and packaging.
- artifact repositoryuses · An artifact repository is a service that stores, versions, and distributes software packages, build outputs, container images, or other versioned artifacts.
- build cacheuses · A build cache stores outputs of completed build tasks so they can be reused in later builds when the relevant inputs have not changed.
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.



