Decoupling

As explained in Learn Docker in a Month of Lunches, Second Edition

Decoupling is a design technique that separates communicating components so they do not depend directly on one another.

Decoupling lets components communicate through a message queue instead of depending on direct communication with one another. A publisher can send messages before a subscriber starts, and a subscriber can keep listening when no publisher is active. Each component works with the queue without knowing about the others, supporting performance and scalability. section 21.1

Figure 21.1 Message queues decouple components so that they don’t communicate with each other directly.

The diagram shows how a message queue separates components that would otherwise communicate directly. section 21.1

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes

Demonstrates asynchronous publishing and subscription through Redis containers, including messages sent before a subscriber listens.

Examples

Uses a Redis publisher and subscriber on channel21 to demonstrate messages passing through a queue.

What you can do after

Apply decoupling by publishing and subscribing through a Redis message queue so components can operate independently.

How it connects

Connects asynchronous communication with message queues, publishers, and subscribers.

liveBookmanning.com

Read Learn Docker in a Month of Lunches, Second Edition on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.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.
• 

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

  liveBookmanning.com
  Grokking ConcurrencyDecoupling is a design technique that separates components or responsibilities to reduce their dependencies on one another.

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 Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.