The Many Faces of Publish/Subscribe.¶
Eugster, P. T., Felber, P. A., Guerraoui, R., & Kermarrec, A. (2003). The Many Faces of Publish/Subscribe. ACM Computing Surveys, 35(2), 114-131.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Message Passing
- Publish Subscribe
- In computing it is the backbone of event-driven architectures — message brokers, the event model of user interfaces, operating-system signals, mailbox-by-topic variants of the actor model.
This sourceCanonical survey defining publish-subscribe and its decoupling of producers and consumers in space, time, and synchronization.
Supported in partVerified against the publisher's abstract
The survey's abstract establishes publish/subscribe as a loosely-coupled distributed communication paradigm and classifies its variants; it says nothing of event-driven architectures, brokers, UI events, signals or actor mailboxes.
“Well adapted to the loosely coupled nature of distributed interaction in large-scale applications, the publish/subscribe communication paradigm has recently received increasing attention.”
- In computing it is the backbone of event-driven architectures — message brokers, the event model of user interfaces, operating-system signals, mailbox-by-topic variants of the actor model.
Mechanisms¶
- Await or Subscription
- Its strength is that it lets a consumer coordinate around a future value without owning any waiting logic — the publish–subscribe posture
This sourceDescribes publish/subscribe as decoupling participants in time and synchronization while delivering published events to interested subscribers.
- Its strength is that it lets a consumer coordinate around a future value without owning any waiting logic — the publish–subscribe posture
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 3 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:b6a038a4887b · see in the full table