Federated Publish/Subscribe Services

Bertelsen, Eirik; Berthling-Hansen, Gabriel; Bloebaum, Trude H.; Duvholt, Christian; Hov, Einar; Johnsen, Frank T.; Morch, Eivind; Weisethaunet, Andreas H.

doi:10.1109/ntms.2018.8328694

Cited by 3 publications

(3 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There are several messaging protocols based on the P/S paradigm. In order to address federated P/S services, (Bertelsen et al, 2018) present a multi-protocol P/S brokering solution. Their solution includes a broker core that acts as a translator between P/S clients using different protocols.…”

Section: Related Workmentioning

confidence: 99%

Publish, Subscribe and Federate!

Spohn¹

2020

Journal of Computer Science

View full text Add to dashboard Cite

Connecting usual things/objects to the Internet allows the monitoring and control of such things from anywhere, which is usually referred to as the Internet of Things (IoT). Things communicate among themselves or with other entities (e.g., a server) so that information can be gathered from things whilst proper actions can be taken upon them. A prominent communication approach adopted by many IoT applications is related to the Publish/Subscribe (P/S) paradigm. Any communication entity willing to provide some data announces its intention to a server (broker), establishing itself as a publisher for such data/topic. Entities that are willing to receive any published data, register themselves to the broker as subscribers. While employing just one broker might lead to a bottleneck and a single point of failure, when having multiple brokers one could end up having difficulties with their management. This work presents a scalable and efficient proposal for the federation of independent brokers, by allowing subscribers to get all their publications no matter to which broker publishers and subscribers are associated with.

show abstract

Section: Related Workmentioning

confidence: 99%

Publish, Subscribe and Federate!

Spohn¹

2020

Journal of Computer Science

View full text Add to dashboard Cite

show abstract

“…The brokers and mediation service (let us call this component a multi-protocol broker) was also Java software. In fact, the multi-protocol broker was an extended version of the federation mechanism described here [18], enhanced for the purpose of this paper to support all the protocols discussed above. For networking, 100 Mbps Ethernet was used, and both Raspberry Pi 3B's were connected to a switch.…”

Section: Testbed Setupmentioning

confidence: 99%

“…In [18], the authors provided a solution for federating between different publish/subscribe protocols, i.e., WSN, MQTT, and AMQP. The work in this paper uses an extended version of that open source implementation with support for additional protocols as the broker and mediation service (aka multiprotocol broker) in the testbed.…”

Section: Related Workmentioning

confidence: 99%

Using Publish/Subscribe for Short-lived IoT Data

Johnsen

2018

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Efficient distribution of IoT sensor data requires one-to-many communication, for which publish/subscribe is a better communication approach than request/response. In this paper, the goal is to identify the/those publish/subscribe protocol(s) that are best suited for IoT data. The premise is that data should be as fresh as possible. Hence, the metric is end-to-end delay and the recommended approach is the solution that yields the lowest delay under the test conditions. Raspberry Pi 3 was used as the testbed, since it is representative as an IoT platform. The protocols evaluated are: AMQP, MQTT, MQTT-SN, STOMP, WSN, and XMPP, as well as using a mediation service to translate between them.

show abstract