How deeply does Grokking Concurrency cover decoupling?

Defines component organization and separates what gets done from when, without detailing implementation steps.

Decoupling

Decoupling is a design technique that separates components or responsibilities to reduce their dependencies on one another.

Decoupling separates unrelated components while grouping related code, organizing complex systems into simpler units that communicate. section 1.3

Concurrency can serve as a decoupling strategy: dividing functionality among modules or units of concurrency separates what gets done from when. This can make components more maintainable and reduce system complexity. section 1.3

How Grokking Concurrency covers it

liveBook manning.com

Read Grokking Concurrency on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Secrets of the JavaScript Ninja, Second EditionA design property in which interacting components know little or nothing about one another's internal details or control flow.
liveBook manning.com

Learn Docker in a Month of Lunches, Second EditionDecoupling is a design technique that separates communicating components so they do not depend directly on one another.
liveBook manning.com

Microsoft Azure in ActionDecoupling is an architectural pattern that reduces direct dependencies between software components so they can operate and scale independently.

Compare how 4 books explain decoupling →

Related concepts

moduleconfigured by · A module is a distinct, bounded software unit that groups related code or functionality and provides an organizational or interaction boundary within a larger system.
autonomyproduces · Autonomy is the capacity or degree to make decisions and act independently within a defined responsibility or set of limits.
don't repeat yourself principleaddressed by · The Don’t Repeat Yourself principle is a software design guideline that gives each piece of knowledge or behavior a single authoritative representation to avoid unnecessary duplication.

This explainer was generated by Manning's knowledge graph from the text of Grokking Concurrency. The section links point to the parts of the book it draws on.