Publish/subscribe model
The publish-subscribe model is a messaging pattern in which publishers send messages without addressing specific recipients, and subscribers receive messages according to their interests or subscriptions.
Apache Kafka in Action
A publish-subscribe model lets publishers send messages to named channels while subscribers independently receive messages from those channels.
- How it is used
- Connects services through asynchronous, topic-based message exchange for streaming data and integration.
- How deep it goes
- Explains producers, consumers, topics, partitions, brokers, persistence, replication, and scaling, but not client implementation details.
- Examples
- Uses finance, manufacturing, retail, fraud detection, inventory management, order processing, and network monitoring examples.
- What you can do after
- Apply it via Apache Kafka to connect producers and consumers, distribute events, and support scalable real-time data flows.
Read how Apache Kafka in Action explains publish/subscribe model →
Object-Oriented Software Design in C++
A communication model in which a publisher provides state or event information to one or more subscribers without depending on their specific behavior.
- How it is used
- Deploys one-to-many event or state distribution when multiple components must react independently to changing content.
- How deep it goes
- Defines notification, content requests, subscription, and coupling, then contrasts them with a hardcoded C++ distributor.
- Examples
- Uses an online news service and baseball hit events feeding log, graph, and table reports.
- What you can do after
- Evaluate/understand how to separate event production from subscriber behavior and recognize hardcoded coupling that prevents independent subscription changes.
Read how Object-Oriented Software Design in C++ explains publish/subscribe model →
Kafka for Architects
A publish-subscribe pattern is a messaging pattern in which publishers send messages to subscribers without requiring direct knowledge of the subscribers.
- How it is used
- Decouples services in asynchronous, event-driven architectures by distributing one event to multiple independent consumers.
- How deep it goes
- Defines producer and subscriber roles, contrasts point-to-point delivery, and addresses routing and governance without implementation walkthroughs.
- Examples
- Uses customer address events, Kafka topics, independent business-service subscribers, and content-based routing into billing and shipping topics.
- What you can do after
- Apply via Kafka by publishing reusable events, subscribing services independently, and routing differently shaped messages through processing services.
Read how Kafka for Architects explains publish/subscribe model →
The Joy of JavaScript
An architecture in which publishers emit events or messages to subscribers without requiring direct coupling between them.
- How it is used
- Uses event-driven streams to separate data production from consumption and replace inefficient polling with notification.
- How deep it goes
- Explains sources, subscribers, push flow, lazy observables, and a custom EventEmitter-backed implementation.
- Examples
- Demonstrates EventEmitter listeners, Node.js readable streams, and a PushArray whose push operation notifies subscribers.
- What you can do after
- Build it from scratch by combining EventEmitter with subscription methods and a next(value) subscriber interface.
Read how The Joy of JavaScript explains publish/subscribe model →
Software Design for Python Programmers
The publisher-subscriber model is a communication pattern in which a publisher produces state or event information and subscribers receive notifications about it.
- How it is used
- Coordinates one publisher with multiple independently processing subscribers when changing state must reach interested components.
- How deep it goes
- Defines notification, fetching, independence, and subscription changes, but does not show implementation code.
- Examples
- Uses online news notifications and baseball hit events feeding logger, table, and graph reports.
- What you can do after
- Evaluate designs for loose coupling, selective content retrieval, and subscriber changes without publisher modifications.
Read how Software Design for Python Programmers explains publish/subscribe model →
Related concepts
- Apache Kafkaimplemented by · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
- producer-consumerequivalent to · The producer-consumer model coordinates components that generate data with components that retrieve and process it, typically through a buffer or queue.
- topicimplemented by · A topic is a named messaging destination or stream to which producers publish messages or records and from which consumers receive or read them.
- observer patternimplemented by · The observer pattern is a behavioral design pattern in which a subject notifies registered observers when its state or activity changes.
- channelkind of · A channel is a medium, mechanism, or pathway through which information or messages are conveyed between participants or endpoints.
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.