liveBook · Manning

Gradle

As explained in Microservices Patterns, Second Edition

An open-source build automation system that models builds as tasks and supports dependency management and incremental execution.

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

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

Compare how 4 books explain Gradle →

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.