Publish–Subscribe pattern
E679878
The Publish–Subscribe pattern is a messaging design pattern in which senders (publishers) broadcast messages without knowledge of specific receivers, and subscribers receive only the messages they have expressed interest in.
All labels observed (4)
| Label | Occurrences |
|---|---|
| Data-Centric Publish–Subscribe | 1 |
| PubSub | 1 |
| Publish–Subscribe pattern canonical | 1 |
| Reactive Messaging | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T7665719 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Publish–Subscribe pattern Context triple: [Observer, alternativeName, Publish–Subscribe pattern]
-
A.
Pub/Sub Lite
Pub/Sub Lite is a lower-cost, high-throughput messaging service on Google Cloud designed for streaming data workloads that can tolerate more operational management compared to standard Pub/Sub.
-
B.
Google Cloud Pub/Sub
Google Cloud Pub/Sub is a fully managed real-time messaging service that enables asynchronous, scalable communication between independent applications and services.
-
C.
JMS
JMS (Java Message Service) is a Java API specification that enables applications to create, send, receive, and read messages in a loosely coupled, asynchronous, and reliable messaging system.
-
D.
CSP (Communicating Sequential Processes)
CSP (Communicating Sequential Processes) is a formal model for describing and analyzing concurrent systems based on independent processes that interact solely through message-passing communication.
-
E.
MQTT
MQTT is a lightweight, publish-subscribe messaging protocol commonly used for reliable communication in IoT and constrained network environments.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Publish–Subscribe pattern Target entity description: The Publish–Subscribe pattern is a messaging design pattern in which senders (publishers) broadcast messages without knowledge of specific receivers, and subscribers receive only the messages they have expressed interest in.
-
A.
Pub/Sub Lite
Pub/Sub Lite is a lower-cost, high-throughput messaging service on Google Cloud designed for streaming data workloads that can tolerate more operational management compared to standard Pub/Sub.
-
B.
Google Cloud Pub/Sub
Google Cloud Pub/Sub is a fully managed real-time messaging service that enables asynchronous, scalable communication between independent applications and services.
-
C.
JMS
JMS (Java Message Service) is a Java API specification that enables applications to create, send, receive, and read messages in a loosely coupled, asynchronous, and reliable messaging system.
-
D.
CSP (Communicating Sequential Processes)
CSP (Communicating Sequential Processes) is a formal model for describing and analyzing concurrent systems based on independent processes that interact solely through message-passing communication.
-
E.
MQTT
MQTT is a lightweight, publish-subscribe messaging protocol commonly used for reliable communication in IoT and constrained network environments.
- F. None of above. chosen
Statements (62)
| Predicate | Object |
|---|---|
| instanceOf |
messaging pattern
ⓘ
software design pattern ⓘ |
| alsoKnownAs |
pub-sub pattern
ⓘ
publish/subscribe pattern ⓘ |
| contrastsWith |
point-to-point messaging
ⓘ
request–response pattern ⓘ |
| decouples |
message producers and message consumers
ⓘ
senders and receivers ⓘ |
| decouplesInDimension |
space
ⓘ
synchronization ⓘ time ⓘ |
| definesRelationshipBetween | publisher and subscriber ⓘ |
| goal |
deliver messages only to interested subscribers
ⓘ
enable flexible system evolution ⓘ reduce coupling between components ⓘ |
| hasKeyConcept |
broker
ⓘ
channel ⓘ event ⓘ event bus ⓘ message ⓘ publication ⓘ publisher ⓘ subscriber ⓘ subscription ⓘ topic ⓘ |
| hasMechanism |
subscriptions based on content
ⓘ
subscriptions based on topics ⓘ |
| hasVariant |
channel-based publish–subscribe
ⓘ
content-based publish–subscribe ⓘ pattern-based publish–subscribe ⓘ topic-based publish–subscribe ⓘ |
| implementedBy |
Amazon SNS
ⓘ
Apache Kafka ⓘ Google Cloud Pub/Sub ⓘ MQTT brokers ⓘ NATS ⓘ RabbitMQ ⓘ Redis Pub/Sub ⓘ |
| influenced |
event sourcing
ⓘ
reactive systems design ⓘ |
| supports |
asynchronous communication
ⓘ
broadcast messaging ⓘ event-driven architecture ⓘ extensibility ⓘ integration of heterogeneous systems ⓘ loose coupling ⓘ many-to-many communication ⓘ one-to-many communication ⓘ scalability ⓘ selective message delivery ⓘ |
| usedIn |
GUI event handling
ⓘ
IoT systems ⓘ distributed systems ⓘ event-driven systems ⓘ financial market data distribution ⓘ logging systems ⓘ microservices architectures ⓘ monitoring systems ⓘ real-time notification systems ⓘ |
| uses |
event bus
ⓘ
message broker ⓘ message queue ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: Publish–Subscribe pattern Description of subject: The Publish–Subscribe pattern is a messaging design pattern in which senders (publishers) broadcast messages without knowledge of specific receivers, and subscribers receive only the messages they have expressed interest in.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: Publish–Subscribe pattern
linked to: Publish–Subscribe pattern
linked to: Publish–Subscribe pattern