Publish-Subscribe: Difference between revisions

From air
Jump to navigation Jump to search
No edit summary
 
(9 intermediate revisions by one other user not shown)
Line 15: Line 15:
* Centralised vs Distributed (P2P, ...)
* Centralised vs Distributed (P2P, ...)
* Atomicity (ACID transaction)
* Atomicity (ACID transaction)
* Broker required or Direct


==Protocols and API==
==Protocols and API==
Line 23: Line 24:
* [[UPnP]] GENA
* [[UPnP]] GENA
* [[MQTT]]
* [[MQTT]]
* [[M3DA]]
* [[PubSubHubBub]]
* [[PubSubHubBub]]
* [[RTPS|Real-Time Publish-Subscribe (RTPS)]]
* [[RTPS|Real-Time Publish-Subscribe (RTPS)]]
Line 28: Line 30:
* [[Robot Operating System]]
* [[Robot Operating System]]
* [[Ivy]]
* [[Ivy]]
* [[Apache Kafka]]
* [[WAMP]]
* [[Redis.io]]


==PubSub-as-a-Service Providers==
* [[PubNub]]
* [[Octoblu]]
* [[Axeda]]
* [[Xively]]
* [https://cloud.google.com/pubsub Google Cloud Pub/Sub]
* [http://superfeedr.com/ Superfeedr]


==Papers==
==Papers==

Latest revision as of 01:52, 15 November 2014

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)
  • Broker required or Direct

Protocols and API

PubSub-as-a-Service Providers

Papers