liveBook · Manning

Sink node

Also called Subscriber, message consumer, event consumer

A sink node is a destination component or endpoint that receives data, messages, events, or flow from an upstream source for consumption or processing.

How 7 Manning books explain it

Learn Docker in a Month of Lunches, Second Edition

A subscriber is a messaging component that listens for and receives messages published to a subject.

How it is used
Receives published messages so independent components can respond to events without direct communication.
How deep it goes
Defines the role, walks through Redis and NATS listeners, and explains missed messages without implementing a subscriber SDK.
Examples
Runs a Redis CLI listener for ping messages and checks a NATS to-do-event subscriber through container logs.
What you can do after
Operate/configure a Redis or NATS subscriber and diagnose missing to-do items by checking for a listener.

Read how Learn Docker in a Month of Lunches, Second Edition explains sink node →

Robotics for Programmers

A ROS subscriber is a ROS node entity that receives messages of a specified type from a topic.

How it is used
Connects ROS nodes to topic-based message streams so components can react to published sensor or application data.
How deep it goes
Defines topics, types, callbacks, middleware decoupling, and rclpy setup, but does not detail callback scheduling internals.
Examples
Uses detected_objects planning, a String subscriber, a counter exercise, custom FooBar messages, and topic-name typo diagnosis.
What you can do after
Operate/configure a subscriber with rclpy, ros2 CLI, callbacks, message types, and topic-inspection tools.

Read how Robotics for Programmers explains sink node →

Grokking Software Architecture

A component that subscribes to topics and receives messages published to them.

How it is used
Uses subscribers as reactive workers in asynchronous, topic-based communication.
How deep it goes
Defines the consumer role and explains ordering, duplicate delivery, idempotency, and failure-handling concerns.
Examples
Uses order-processing subscribers and an asynchronous AI support agent to illustrate distinct reactions to events.
What you can do after
Evaluate consumer designs for decoupling, delayed results, ordering, and duplicate delivery.

Read how Grokking Software Architecture explains sink node →

Spring Start Here, Second Edition

A subscriber is a reactive component that attaches to a producer and consumes its eventual result.

How it is used
Defines a task’s dependency on another task by attaching to its producer and consuming its eventual result.
How deep it goes
Defines producer and subscriber roles and traces a WebClient subscription chain, but does not explain subscriber internals.
Examples
Uses a WebClient payment request and its request-body task to illustrate chained subscriptions.
What you can do after
Understand how one reactive task consumes another task’s result while expressing a dependency without keeping a thread waiting.

Read how Spring Start Here, Second Edition explains sink node →

Software Design for Python Programmers

A subscriber is a software component that receives notifications from a publisher and may request and process the publisher's new content.

How it is used
Coordinates independent consumers of publisher-generated content without coupling the publisher to subscriber implementations.
How deep it goes
Defines notification, optional retrieval, processing, and subscription behavior, stopping short of a full decoupled implementation.
Examples
Uses news readers and baseball log, table, and graph report generators as subscriber examples.
What you can do after
Apply the subscriber role when designing components that independently consume publisher events.

Read how Software Design for Python Programmers explains sink node →

Advanced Algorithms and Data Structures

A sink is the distinguished network vertex into which flow is delivered and which has no outbound flow.

How it is used
Defines the destination of flow in a network and the endpoint whose delivered flow the maximum-flow problem seeks to maximize.
How deep it goes
Defines the sink by its incoming-only edges and role in maximum flow, without detailing implementation.
Examples
Illustrates the sink as the destination in a network diagram and uses water flowing through pipes as an analogy.
What you can do after
Understand the sink’s role as the destination vertex in a maximum-flow network.

Read how Advanced Algorithms and Data Structures explains sink node →

JavaScript in Depth

The component that receives and processes values supplied by a data-producing component.

How it is used
Receives and processes streamed values at the pipeline’s destination.
How deep it goes
Defines the consumer’s role and pipeline position without detailing sink-specific implementation.
Examples
Uses files, databases, and outbound HTTP requests or responses as destinations, including requests receiving streamed bodies.
What you can do after
Understand where streamed data ends up and distinguish producer-initiated push from consumer-initiated pull.

Read how JavaScript in Depth explains sink node →

Also covered in

What to know first

Related concepts

Questions about sink node

What is sink node?

A sink node is a destination component or endpoint that receives data, messages, events, or flow from an upstream source for consumption or processing.

Which Manning books explain sink node?

Learn Docker in a Month of Lunches, Second Edition, Robotics for Programmers, Grokking Software Architecture, Spring Start Here, Second Edition, Software Design for Python Programmers, Advanced Algorithms and Data Structures and JavaScript in Depth.

What should I know before learning sink node?

Manning books that teach sink node usually introduce producer, topic, message and data integrity first.

What is sink node a kind of?

Sink node is a kind of driving adapter. A driving adapter receives input from an external actor or system, translates it into application terms, and invokes an application input port.

What is sink node also called?

Sink node is also called Subscriber, message consumer or event consumer.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.