Schedule a demo

Blog

All IoT Strategy IoT Orchestration Case Study Azure News System integrators
  • How IoT is Transforming Smart Shopping
  • Turning Retail Pain into Smart Gain
  • Another Big Win for Axonize & Deutsche Telekom
  • Insights from 1,300 IoT projects in 2018 & What to Expect in 2019
  • Smart city orchestration in action – connecting all city smart apps
  • IoT Sensors & Bundles & Platforms, Oh My!
  • Break Your Sensors Out of Their Silos
  • Achieving in-transit visibility in complex supply chains
  • Case Study: How Megla is Implementing IoT to Unleash Data
  • Growing Gains: Microsoft on scaling to hundreds of microservices
  • Axonize launches partnership with Singtel and enters the Asian and Australian markets
  • Case Study: How Groupe Tera is Using IoT to Measure Air Quality Sensor Data
  • Case Study: Deutsche Telekom Selects the Axonize IoT Orchestration Platform
  • Case Study: How Optus is Using IoT to Disrupt the Retail Industry in Australia
  • Diving into Edge Computing
  • AXONIZE SELECTED AS ONE OF THE TOP IOT STARTUPS OF 2018
  • Case Study: Fast Food Chain Saves 27% on energy consumption
  • Case Study: Hotel Improves Efficiency & Customer Experience with IoT
  • Case Study: Presidential House Installs Comprehensive Monitoring of Mission Critical Server Room
  • POPULAR IOT PROTOCOLS 2018: AN OVERVIEW & COMPARISON [Updated]
  • Deutsche Telekom IoT Leadership Visits Bezeq & Axonize
  • Accelerating time-to-market by 90% with Microsoft Azure
  • Axonize Wins Deutsche Telekom Investment for Innovative IoT Platform
  • Using IoT Orchestration to Break Down the Silos
  • What is IoT orchestration?
  • How facility managers are "smartifying" their buildings for increased profitability
  • Case Study: How Bezeq is ‘Smartifying’ Kindergartens & Schools
  • The 4 keys to starting small and scaling successfully in IoT
  • IoT revenue is in the application development for service providers
  • Most Popular IoT Use Case? Smart Energy Management
  • Everything You Need to Know: Deloitte's The Building of the Future Meetup
  • Axonize named one of the top 10 most disruptive companies
  • What is an IoT Platform & When to Use One
  • Popular IoT protocols: An overview & comparison
  • Case Study: Leading Israeli service provider Bezeq chooses Axonize to deliver digital business services
  • The most frequently asked IoT questions
  • How System Integrators are growing their IoT business these days
  • The survey results are in: Integrators’ top roadblocks to IoT business growth
  • In It To Win IT: How to get to a live IoT project in 4 days
  • In it to win it: why system integrators should be taking over IoT
  • Joining Collections in MongoDB using the C# driver and LINQ
  • Simple or sophisticated? What kind of IoT platform do you need?
  • The Benefits & Downfalls of Using Azure Stream Analytics for IOT Applications
  • The Case for A Smart Campus, From Someone Who Would Benefit
  • The Top 3 Considerations in Evaluating and Selecting an IoT Platform


It’s time to peek behind the scenes of connected things and talk about the protocols used in IoT.
The IoT protocol world is complex – legacy protocols, emerging technologies, different layering methodologies and many use cases. There are hundreds of protocols, too many to compare them all.
We focused on data transmitting protocols, comparing 5 of the most used IoT protocols.
Before we dig in, let’s go over a couple of basic terms:

  1. Overhead- an excess or indirect computation time, memory, bandwidth, or other resources that are required to attain a particular goal.
  2. Latency – a delay between the stimulation and response.

There are protocols we aren’t discussing today but will occasionally show up in IoT applications:

  1. HTTP – the foundational protocol of the WWW but, limited usefulness for IoT because it doesn’t support bi – directional communication and has high overhead.
  2. TCP & UDP – Old kids on the block, most of the IoT protocols based on these 2 and add IoT-specific features on top of the basic protocols.

 

Protocol Advantages Disadvantages
MQTT
  • Easy to implement
  • Useful for connections with remote location
  • Small code footprint
  • Lightweight
  • Asymmetric client -server relationship
  • No error-handling
  • Hard to add extensions
  • Basic message queuing implementations
  • Doesn’t address connection security
CoAP
  • Multicast support
  • Low overhead
  • Minimizing complexity of mapping with HTTP
  • Communication models flexibility
  • Low latency
  • Doesn’t enable communication level security
  • Few existing libraries and solution support
AMQP
  • Complex message queuing implementations
  • ISO standard
  • High routing reliability and security
  • Easly extensible
  • Symmetric client-server relationship
  • Bigger packet size than other protocols.
  • Doesn’t support Last Value Queue (LVQ)
Websocket
  • Simplifies the web communication and co – network compatibility
  • Connection management
  • Specific  hardware  requirements
  • No useful open source implementations targeted at embedded systems
XMPP-IoT
  • Real-time
  • Low latency
  • Easily understandable
  • Easly extensible
  • Any XMPP server may be isolated
  • XML-based  protocol,  heavy data  overhead
  • Not suitable for embedded IoT applications

 

Our own platform can handle any of these protocols and many more. We’ve implemented a protocol and data gateway as part of our platform, that can connect to any protocol, current or future. The gateways standardize communication and data within the Axonize cloud.

Let’s get your device connected – email us helllo@axonize.com