How deeply does Software Design for Python Programmers cover publish/subscribe model?

Defines notification, fetching, independence, and subscription changes, but does not show implementation code.

Publish/subscribe model

As explained in 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.

The publish/subscribe model separates a publisher that produces state or event information from subscribers that process notifications independently. The publisher does not know how subscribers are implemented or what they do with the content. section 12.0 section 12.2

Baseball game reports

A baseball reporter publishes each hit or out as it occurs. A logger records events immediately, while table and graph generators accumulate information and report after the game. Each subscriber handles the same events differently. section 12.1

A flexible design lets the system:

Create content at arbitrary times and notify every current subscriber immediately. section 12.1.1
Let subscribers fetch content selectively and process it however they choose. section 12.1.1
Add or remove subscribers without changing the publisher’s code. section 12.1.1 section 12.2

How Software Design for Python Programmers covers it

Cover of Software Design for Python Programmers

liveBook manning.com

Read Software Design for Python Programmers on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Apache Kafka in ActionA publish-subscribe model lets publishers send messages to named channels while subscribers independently receive messages from those channels.
liveBook manning.com

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.
liveBook manning.com

Kafka for ArchitectsA publish-subscribe pattern is a messaging pattern in which publishers send messages to subscribers without requiring direct knowledge of the subscribers.
liveBook manning.com

The Joy of JavaScriptAn architecture in which publishers emit events or messages to subscribers without requiring direct coupling between them.

Compare how 5 books explain 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.

This explainer was generated by Manning's knowledge graph from the text of Software Design for Python Programmers. The section links point to the parts of the book it draws on.