Publish-Subscribe

A messaging pattern where publishers emit messages to topics and subscribers receive messages from those topics.

Motivation

Publish-Subscribe is useful because it gives engineers a precise handle on a recurring problem: a messaging pattern where publishers emit messages to topics and subscribers receive messages from those topics.. It helps you decide what to pay attention to, what abstractions are available, and which tradeoffs matter in real systems.

Where it fits

Publish-Subscribe belongs to the Software track, inside the Distributed Systems layer. In the knowledge graph, this places it near concepts that explain the same level of abstraction and the neighboring ideas it depends on.

Mental model

Think of Publish-Subscribe as one piece of the larger computing map. It is easiest to understand when you ask two questions: what problem does it solve, and what assumptions does it make about the concepts below it?

Subconcepts

Publisher

The component that emits messages to a topic.

Subscriber

The component that receives messages from a topic.

Topic

A named channel used to group messages for subscribers.

Subscription

A subscriber registration for one or more topics.

Common mistakes

Using Publish-Subscribe as a buzzword without understanding the problem it solves.
Learning the definition in isolation instead of connecting it to nearby concepts.

Requires: Message Queue