googlepluslinkedintwitterfacebookcircle-righticon-circle-leftcircle-downreliabilitystartedicon-statusdoclibraryapiforumsuperpowersspaceshipglobaledgecommsolutionsbusinesstrustshieldlightbulbhardwarelargeportingapplicationshardwareapi2libraryapisecureopensourceportable< path class="cls-1" d="M2022.62,683.81a1.39,1.39,0,1,1,1.39-1.39A1.39,1.39,0,0,1,2022.62,683.81Zm0-1.5a0.11,0.11,0,0,0-.11.11c0,0.12.21,0.12,0.21,0A0.11,0.11,0,0,0,2022.62,682.31Z" transform="translate(-2008.95 -661.67)" />securedevcommunitylightningclockdiscoveraccessscalablesolutionsadminsolutionsmonitoringdatadiscoveryresourceusageanalyticstoolwebbuildermobilebuilderdashbuilderdatastorageidentityanalyticsenginedevicemanagementdevlibrarysecureconnectionsopenaccesshostingfederatedbuildergatewaydevicecloudembeddedsdkmarketplacesecuritymanagementcalendareyecreate-manage-iconcertifiedqualityusagebillingaccesscontrolexositereadylogolgconnectedproductconnectedsolutionconnectedbusinescomingsoonhomeresourcesdeveloperhomeresourceswhitepaperhomeresourcescasestudy

Embedded IoT Protocols Guide Part II: The Old Standards of XMPP

embedded iot protocols guide part II the old standards of xmpp

In any scalable IoT system it is important to use an embedded protocol that can handle the workload while doing it efficiently. In this week’s breakdown of the Embedded IoT Protocols white paper, written by Patrick Barrett, we will be looking at the benefits and implications of XMPP.

BENEFITS OF THE PROTOCOL FORMALLY KNOWN AS JASPER

XMPP, previously known as Jabber, is a protocol originally designed for use in instant messaging. Early IoT developers were interested in XMPP because of its real-time nature. It provides low latency communication back to a single, central server. Exosite offers an XMPP-based API that was developed for use in IoT deployments patters where latency is the highest priority.

HEAVY DATA OVERHEAD

However, XMPP has a number of problems that make it somewhat undesirable for embedded IoT protocols. As an XML-based protocol, XMPP is very verbose, even more so than HTTP, and has heavy data overhead. A single request/response exchange to send one byte of data from an IoT connected device to the server is more than 0.5 kB.

There is a draft specification that would compress XMPP using an XML encoding called efficient XML Interchange (EXI). But even with EXI, the same one byte of data gets hundreds of bytes of protocol overhead from XMPP alone. EXI is also a much harder format to process than other options now available. Because of these inherent problems, it is generally recommended to avoid using XMPP in embedded IoT applications.

Download the full white paper for further IoT insight into embedded protocols or contact us to jump-start your IoT strategy today.



New Call-to-action



1 Like

Send Us a Question

SalesProduct Support

Call our Sales Team

612.353.2161