Publish-subscribe
Publish-subscribe distributes published messages to interested subscribers without requiring the sender to contact each one directly.
Multiple subscriptions receive the same notification
Publish-subscribe, or Pub/Sub, is a messaging pattern. A publisher publishes a message; an intermediary distributes it to matching subscriptions. In a fictional example, both the catalogue and search index must react after product approval. The applications therefore have separate subscriptions.
This differs from multiple workers on the same work queue: they normally share tasks rather than each performing every task. Check whether every subscriber required by the business has processed successfully. Catalogue success does not confirm the search index. Retention, redelivery and reading past messages are product features and settings, not blanket Pub/Sub guarantees.
Sources
Related terms
- Message queueA message queue buffers messages until a consumer takes them for processing.
- Message brokerA message broker accepts messages and routes them to recipients according to defined rules.
- Event-driven architectureIn event-driven architecture, components report events that other components can respond to independently.
- Server-sent eventsServer-sent events carry text notifications from server to client over HTTP, for example about the progress of a background job.
- Entity tagAn ETag identifies a particular representation version of an HTTP resource and supports conditional reads or changes.
- Cross-Origin Resource SharingCORS controls browser access to responses across origin boundaries. It replaces neither API login nor permission checks.
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.