JAX 2014 - M2M for Java Developers with MQTT
15 likes7,484 views
The document provides an overview of MQTT, a messaging protocol designed for Machine-to-Machine (M2M) communication and the Internet of Things (IoT), highlighting its architecture, features, and use cases. It discusses MQTT's benefits such as low bandwidth consumption, reliability, and its publish/subscribe model, as well as the quality of service levels it offers. Additionally, it covers historical context, challenges, and various MQTT brokers and clients available for developers.
![Some statistics
2010 2015 2020
~6.909.000.000 ~7.302.000.000 ~7.675.000.000
~12.500.000.000 ~25.000.000.000 ~50.000.000.000
[1]Source: http://www.un.org/esa/population/publications/wpp2008/wpp2008_highlights.pdf
[1]
[2]Source: http://share.cisco.com/internet-of-things.html
[2]](https://image.slidesharecdn.com/jax2014m2mjavadevelopers-140515061834-phpapp02/85/JAX-2014-M2M-for-Java-Developers-with-MQTT-14-320.jpg)
![MqttClient client = new MqttClient(
"tcp://localhost:1883", //URI
"publisher", //Client ID
new MemoryPersistence()); //Persistence
MqttConnectOptions connOptions =
new MqttConnectOptions();
connOptions.setKeepAliveInterval(120);
connOptions.setWill("help/I/died",
new byte[0], 2, true);
connOptions.setCleanSession(false);
connOptions.setUserName("username");
connOptions.setPassword("passw".toCharArray());
client.connect(connOptions);](https://image.slidesharecdn.com/jax2014m2mjavadevelopers-140515061834-phpapp02/85/JAX-2014-M2M-for-Java-Developers-with-MQTT-121-320.jpg)
JAX 2014 - M2M for Java Developers with MQTT
- 1. Dominik Obermaier | dc-square GmbH M2M for Java Developers with MQTT
- 2. About me Hi, I’m Dominik Obermaier. • CTO of dc-square • HiveMQ architect • helped standardizing MQTT at OASIS • Speaker and author about MQTT, M2M and IoT @dobermai
- 6. • Macbook E-Mail Stockphoto https://flic.kr/p/aERxbF
- 10. • Imagine Bild
- 11. • Internet of Things Internet of Things
- 12. The Internet of Things (IoT) refers to uniquely identifiable objects and their virtual representations in an Internet-like structure
- 14. Some statistics 2010 2015 2020 ~6.909.000.000 ~7.302.000.000 ~7.675.000.000 ~12.500.000.000 ~25.000.000.000 ~50.000.000.000 [1]Source: http://www.un.org/esa/population/publications/wpp2008/wpp2008_highlights.pdf [1] [2]Source: http://share.cisco.com/internet-of-things.html [2]
- 15. Some statistics 0 12,500,000,000 25,000,000,000 37,500,000,000 50,000,000,000 2010 2015 2020 People Things
- 16. Some statistics 0 12,500,000,000 25,000,000,000 37,500,000,000 50,000,000,000 2010 2015 2020 People Things 1.8x
- 17. Some statistics 0 12,500,000,000 25,000,000,000 37,500,000,000 50,000,000,000 2010 2015 2020 People Things 1.8x 3.4x
- 18. Some statistics 0 12,500,000,000 25,000,000,000 37,500,000,000 50,000,000,000 2010 2015 2020 People Things 1.8x 3.4x 6.5x
- 25. TECHNOLOGY THAT SUPPORTS WIRED OR WIRELESS COMMUNICATION BETWEEN DEVICES
- 27. Why now?
- 30. Screenshot Taken from Oracle JavaOne Strategic Keynote 2013
- 31. Are we there yet? https://flic.kr/p/5WR2fd
- 32. Challenges Security Identity Management Interoperability Privacy Provisioning Scalability BIG Data Device Management ...
- 33. Protocols?
- 35. ‣ efficient in bandwidth ‣ scalable ‣ standardized ‣ open ‣ data agnostic ‣ must be suited for constrained devices AND server infrastructure Requirements for an IoT Protocol
- 36. Request / Response Verbose Polling instead of Push No quality of service How to get notified if clients die? Stateless HTTP?
- 38. What is MQTT ‣ Messaging Protocol ‣ Simple ‣ On top of TCP ‣ Publish / Subscribe Architecture ‣ Binary protocol ‣ Minimal Overhead ‣ Designed for unreliable networks ‣ Data agnostic
- 39. Use cases ‣ Push instead of Poll ‣ Bandwidth is at a premium ‣ Enterprise applications should interact with mobile applications ‣ Reliable delivery of messages over unreliable networks ‣ Constrained devices ‣ Low latency
- 40. Features ‣ Topic Wildcards ‣ 3 Quality of Service Levels ‣ Retained Messages ‣ Last Will and Testament ‣ Persistent Sessions ‣ Heartbeats
- 43. MQTT Topics
- 44. ‣ Hierarchical ‣ Very lightweight ‣ Subtopic-Level Wildcards (+) ‣ Subtree-Level Wildcards (#) ‣ Max 64.000 characters ‣ Clients can publish / subscribe to N topics ‣ Brokers can queue for topics if QoS > 0 MQTT Topics
- 45. MQTT Topics
- 66. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/awesome
- 67. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/awesome
- 68. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/awesome
- 69. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/awesome
- 70. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/awesome
- 71. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/awesome
- 72. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/awesome
- 73. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 74. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 75. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 76. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 77. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 78. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 79. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 80. MQTT Topic Level Wildcard MQTT Bacon is awesome looks fantastic +/is/+
- 81. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 82. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 83. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 84. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 85. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 86. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 87. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 88. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 89. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic MQTT/#
- 90. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 91. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 92. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 93. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 94. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 95. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 96. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 97. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 98. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 99. MQTT Subtree Wildcard MQTT Bacon is awesome looks fantastic #
- 100. Quality of Service Levels QoS 0 At most once delivery The message is delivered once or never. QoS 1 At least once delivery The message is delivered once or more. QoS 2 Exactly once delivery The message is delivered exactly once.
- 101. Last Will and Testament ‣ Clients can specify a LWT ‣ Broker publishes the LWT message on behalf of the client on “death” ‣ Useful for reporting problems ‣ Real push on device “death” ‣ Mostly used for reporting the connection status of a device
- 102. Retained messages ‣ Last known good value ‣ Last message is stored for a topic ‣ Publishing clients decide if the message should be retained ‣ Clients automatically receive the retained message after subscribing
- 103. Security Protocol ‣ Username / Password ‣ Payload Encryption Transport ‣ TLS ‣ Client certificate authentication Broker ‣ Publish / Subscribe Permissions ‣ Integration to other systems (databases, APIs, ....)
- 104. History 1999 2010 2013 2014 MQTT invented by IBM and Arcom (Eurotech) royalty free OASIS TC formed MQTT is OASIS standard
- 105. Real world use cases
- 106. Use case: ‣ more than 850M Facebook Messenger Users ‣ Chat application ‣ Improved Battery ‣ Lower latency ‣ Less bandwidth https://www.facebook.com/notes/facebook-engineering/building-facebook-messenger/10150259350998920 Facebook Messenger
- 107. Use case: ‣MQTT as central message “bus” ‣ Easy to integrate with other technologies ‣ Remote monitoring ‣ Many open source Smart Home Frameworks support MQTT ‣ Remote control Smart Home
- 108. Use case: ‣30.000 devices ‣ 17.000 km pipeline ‣ Remote monitoring ‣ Remote control ‣ Uses satellite links ‣ Bandwidth is very expensive Pipelines
- 109. Gaining traction Google Trends - 2014/05/13
- 110. MQTT Brokers
- 111. Mosquitto ‣ Open Source ‣ Ideal for running in constrained environments ‣ Supports Bridging ‣ Written in C
- 112. HiveMQ ‣ High Performance MQTT broker ‣ Native Websockets Support ‣ Java Plugin System ‣ Clustering ‣ Bridging ‣ Scalable to > 100.000 connections
- 113. Other brokers + Many others see https://github.com/mqtt/mqtt.github.io/wiki/brokers
- 115. Bridging
- 116. Clustering
- 117. Broker comparison QoS 0 QoS 1 QoS 2 Auth Bridge $SYS SSL dynamic topics cluster websockets plugins HiveMQ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ mosquitto ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ X X ✔ RSMB ✔ ✔ ✔ ✔ ✔ ✔ X ✔ X X X RabbitMQ ✔ ✔ X ✔ X X ✔ ✔ ? ? ? ActiveMQ ✔ ✔ ✔ ? X X ? ? ? ✔ ?
- 118. MQTT Clients
- 119. Eclipse Paho ‣ Open Source ‣ “Reference Implementation” ‣ Available in many languages: Java, Javascript, Lua, C, C++, Go, Python ‣ The JS library uses websockets ‣ Active Community
- 120. MqttClient client = new MqttClient( "tcp://localhost:1883", //URI "publisher", //Client ID new MemoryPersistence()); //Persistence client.connect(); client.publish("the/topic", //topic "message".getBytes(), //message 1, //QoS false); //retained client.disconnect();
- 121. MqttClient client = new MqttClient( "tcp://localhost:1883", //URI "publisher", //Client ID new MemoryPersistence()); //Persistence MqttConnectOptions connOptions = new MqttConnectOptions(); connOptions.setKeepAliveInterval(120); connOptions.setWill("help/I/died", new byte[0], 2, true); connOptions.setCleanSession(false); connOptions.setUserName("username"); connOptions.setPassword("passw".toCharArray()); client.connect(connOptions);
- 122. MqttAsyncClient client = new MqttAsyncClient(...); client.connect(null, new IMqttActionListener() { @Override public void onSuccess(IMqttToken asyncActionToken) { try { client.publish(...); } catch (MqttException e) {} } @Override public void onFailure(IMqttToken asyncActionToken, Throwable exception) {} }); client.disconnect();
- 123. final MqttClient client = new MqttClient(...); client.setCallback(new MqttCallback() { @Override public void connectionLost(Throwable cause) {} @Override public void messageArrived(String topic, MqttMessage message)throws Exception { System.out.println(new String(message.getPayload())); } @Override public void deliveryComplete(IMqttDeliveryToken token) {} }); client.connect(); client.subscribe("#");
- 124. Fusesource MQTT Client ‣ Java ‣ 3 API Styles ‣ Very easy to intercept ‣ Based on HawtIO ‣ Very performant ‣ In Maven Central
- 125. MQTT mqtt = new MQTT(); mqtt.setHost("localhost", 1883); mqtt.setClientId("clientId"); mqtt.setCleanSession(false); mqtt.setWillTopic("willtopic"); mqtt.setWillMessage("willmessage"); mqtt.setWillQos(QoS.EXACTLY_ONCE); mqtt.setUserName("user"); mqtt.setPassword("passwd"); BlockingConnection conn = mqtt.blockingConnection(); conn.connect();
- 126. MQTT mqtt = new MQTT(); BlockingConnection conn = mqtt.blockingConnection(); conn.connect(); conn.publish("the/topic", //topic "message".getBytes(), //message QoS.EXACTLY_ONCE, //QoS false); conn.disconnect();
- 127. MQTT mqtt = new MQTT(); FutureConnection conn = mqtt.futureConnection(); Future<Void> connectFuture = conn.connect(); // funky business logic connectFuture.await(); conn.publish("the/topic", //topic "message".getBytes(), //message QoS.EXACTLY_ONCE, //QoS false). then(new Callback<Void>() { @Override public void onSuccess(Void value) { System.out.println("Success"); } @Override public void onFailure(Throwable value) {}});
- 128. MQTT mqtt = new MQTT(); CallbackConnection conn = mqtt.callbackConnection(); conn.connect(new Callback<Void>() { @Override public void onSuccess(Void value) { conn.publish("the/topic", //topic "message".getBytes(), //message QoS.EXACTLY_ONCE, //QoS false, //retain new Callback<Void>() { @Override public void onSuccess(Void value) { System.out.println("Published"); } @Override public void onFailure(Throwable value) {} }); } @Override public void onFailure(Throwable value) {}});
- 130. MQTT over Websockets
- 131. ‣ Every Browser is a ‘device’ ‣ Device-to-Browser Push ‣ Broadcasting to all online users ‣ Detect if a user is offline ‣ Direct Browser-to-device push ‣ Minimum payload ‣ No application-specific protocol MQTT over websockets
- 133. Thanks! @dobermai