Sink node
A sink node is a terminal or receiving component in a data or flow system that accepts incoming data, messages, or flow for consumption, processing, or storage.
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 →
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 →
Related concepts
- data streamkind of · A data stream is an ordered sequence of data items or events made available incrementally for consumption or processing.
- MockConsumerimplemented by · MockConsumer is a Kafka client test class that simulates a consumer without reading records from a live Kafka broker.
- messageuses · A message is a discrete unit of information or data represented, processed, or exchanged in a communication context.
- topicuses · A topic is a named messaging destination or stream to which producers publish messages or records and from which consumers receive or read them.
- reactive streampart of · Reactive Streams is a standard defining interfaces and signaling rules for asynchronous stream processing with nonblocking backpressure between producers and consumers.
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.