Publish-Subscribe: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 23: | Line 23: | ||
* [[UPnP]] GENA |
* [[UPnP]] GENA |
||
* [[MQTT]] |
* [[MQTT]] |
||
* [[M3DA]] |
|||
* [[PubSubHubBub]] |
* [[PubSubHubBub]] |
||
* [[RTPS|Real-Time Publish-Subscribe (RTPS)]] |
* [[RTPS|Real-Time Publish-Subscribe (RTPS)]] |
||
| Line 28: | Line 29: | ||
* [[Robot Operating System]] |
* [[Robot Operating System]] |
||
* [[Ivy]] |
* [[Ivy]] |
||
==Papers== |
==Papers== |
||
Revision as of 10:13, 2 December 2013
Principles
Subscribers subscribe to messages containing events, sensor measurements, alerts, alarms, notifications, ...
Subscription could be done a topic or a topic pattern or on a message content.
Publishers publish messages on a topic or a set of topics
Features
- Content-based routing
- TCP or UDP or Multicast UDP or Broadcast (in LAN) or mix
- LAN or WAN
- Realtime or not
- QoS or not (order, reliability, high-availability ...)
- Centralised vs Distributed (P2P, ...)
- Atomicity (ACID transaction)
Protocols and API
- OSGi EventAdmin Service
- JMS
- AMQP
- CORBA Data Distribution Service
- UPnP GENA
- MQTT
- M3DA
- PubSubHubBub
- Real-Time Publish-Subscribe (RTPS)
- Siena
- Robot Operating System
- Ivy
Papers
- The Many Faces of Publish/Subscribe http://www.cs.ru.nl/~pieter/oss/manyfaces.pdf
- International Conference on Distributed Event-Based Systems (DEBS) http://www.debs.org/