Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
HOW TO IMPROVE ON 
MQTT 3.1.1 
Tim Kellogg 
@kellogh 
MQTT: An Implementor’s Perspective 
AOL Keywords: vasters mqtt
MQTT 
Servers 
Wired 
Networks 
Vertically 
scaled
fuel 
loca-tion 
Funnel Protocol 
temp 
Kafka | AMQP | HTTP
MQTT 
“Uptime” isn’t straightforward 
“Exactly Once” Violates CAP 
Security Problems 
• Retained messages 
• Provenance 
E...
CAP Theorem 
Availability 
Network 
Partitions 
Consistency CP 
AP
CAP Theorem 
Availability 
Partition 
Tolerance 
Guaranteed 
In-Order 
Delivery 
CP 
AP
Subscriber dies prematurely 
Receive 
• Via QoS 2 
Do Work 
• Not 
idempotent 
work 
• Duplicate 
message 
would 
cause 
e...
Subscriber dies prematurely (2) 
Receive 
• Via QoS 2 
ACK 
• Auto-acknowledge 
Crash 
• Before work 
is done
MQTT Recommendations 
Message Dedup 
• Have clients implement “QoS 2” via QoS 1 
Token-based Security 
Provenance story 
M...
CoAP-PubSub 
Resource Directory 
Garbage Collection 
Polling Allowed 
Retained Messages 
Error Codes
QUESTIONS? 
@kellogh 
app.thingfabric.com 
mqtt.io – No Bullshit, Just MQTT™ 
coap.io – No Bullshit, Just CoAP-PubSub™
Prochain SlideShare
Chargement dans…5
×

ThingMonk 2014: How To Improve On MQTT 3.1.1

1 043 vues

Publié le

The MQTT protocol has become possibly the most important IoT protocol, so I think this is an appropriate time to discuss changes for the next version that address problems horizontally scaling brokers experience. This builds off of Clemens Vasters' blog, "MQTT: An Implementor's Perspective" and tries to frame it into a 20 minute format for ThingMonk 2014 in London.

Publié dans : Internet
  • Soyez le premier à commenter

ThingMonk 2014: How To Improve On MQTT 3.1.1

  1. 1. HOW TO IMPROVE ON MQTT 3.1.1 Tim Kellogg @kellogh MQTT: An Implementor’s Perspective AOL Keywords: vasters mqtt
  2. 2. MQTT Servers Wired Networks Vertically scaled
  3. 3. fuel loca-tion Funnel Protocol temp Kafka | AMQP | HTTP
  4. 4. MQTT “Uptime” isn’t straightforward “Exactly Once” Violates CAP Security Problems • Retained messages • Provenance Error Handling
  5. 5. CAP Theorem Availability Network Partitions Consistency CP AP
  6. 6. CAP Theorem Availability Partition Tolerance Guaranteed In-Order Delivery CP AP
  7. 7. Subscriber dies prematurely Receive • Via QoS 2 Do Work • Not idempotent work • Duplicate message would cause errors Crash • ACK isn’t sent
  8. 8. Subscriber dies prematurely (2) Receive • Via QoS 2 ACK • Auto-acknowledge Crash • Before work is done
  9. 9. MQTT Recommendations Message Dedup • Have clients implement “QoS 2” via QoS 1 Token-based Security Provenance story Metadata about messages Error codes
  10. 10. CoAP-PubSub Resource Directory Garbage Collection Polling Allowed Retained Messages Error Codes
  11. 11. QUESTIONS? @kellogh app.thingfabric.com mqtt.io – No Bullshit, Just MQTT™ coap.io – No Bullshit, Just CoAP-PubSub™

×