Description: The Streaming message exchange pattern involves the continuous flow of data between a producer and a consumer over time. Unlike the request-response pattern, streaming supports real-time data transfer where a large volume of data can be processed incrementally, as it arrives. The consumer does not need to wait for the entire dataset to be available before acting on it, making it suitable for real-time applications. Publisher: Based on largely adopted standards Source: https://www.confluent.io/learn/data-streaming/ Last modification: 2024-01-28 Identifier: http://data.europa.eu/dr8/StremmingMessagePatternInteroperabilitySpecificationContract LOST view: Technical view - application EIRA concept: eira:SolutionBuildingBlock Additional identifier: http://data.europa.eu/dr8/StremmingMessagePatternInteroperabilitySpecificationContract ABB name: eira:StremmingMessagePatternInteroperabilitySpecificationContract 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: Key Points: 1) Continuous flow of data over time; 2) Suitable for real-time processing; 3) Common in scenarios with large datasets or real-time updates.