Description: The Publish-Subscribe message pattern refers to ne input channel that splits into multiple output channels, one for each subscriber. When an event is published into the channel, the Publish-Subscribe Channel delivers a copy of the message to each of the output channels. Each output channel has only one subscriber, which is only allowed to consume a message once. In this way, each subscriber only gets the message once and consumed copies disappear from their channels. Publisher: Enterprise Patterns Source: https://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html Last modification: 2024-01-28 Identifier: http://data.europa.eu/dr8/PublishSubscribeMessagePatternInteroperabilitySpecificationContract LOST view: Technical view - application EIRA concept: eira:SolutionBuildingBlock Additional identifier: http://data.europa.eu/dr8/PublishSubscribeMessagePatternInteroperabilitySpecificationContract ABB name: eira:PublishSubscribeMessagePatternInteroperabilitySpecificationContract EIF Layer: N/A Interoperability Dimension: Behavioral IoP Interoperability Saliency: The interoperability specification ABB is salient for legal interoperability because it establishes the normative statements for ensuring interoperability in public services. This ABB is salient for organizational interoperability by establishing the business principles to exchange data between public services. The Interoperability specification ABB is salient for semantic interoperability too in terms of identifying technical standards for the exchange of information between public services. And finally, the ABB is salient for technical interoperability due to it determines the technical requirements to implement the interoperability between public services. Additional information: A Publish-Subscribe Channel can be a useful debugging tool. Even though a message is destined to only a single receiver, using a Publish-Subscribe Channel allows you to eavesdrop on a message channel without disturbing the existing message flow. Monitoring all traffic on a channel can be tremendously helpful when debugging messaging applications. It can also save you from inserting a ton of print statements into each application that participates in the messaging solution. Creating a program that listens for messages on all active channels and logs them to a file can realize many of the same benefits that a Message Store brings.