Jump to content


Application Protocol

http websocket protocol mqtt

  • Please log in to reply
1 reply to this topic

#1 bontorhumala



  • Members
  • Pip
  • 1 posts

Posted 04 June 2014 - 01:58 PM

I recently discovered Carriots and I am impressed with the platform features. However, I am unsure about the transport mechanism: HTTP. From what I heard about IoT, network availability and bandwidth is critical issue. Therefore, the load of HTTP request from device will be costly. Here are some reference that I am sure you guys have also considered:


1. http://www.m2mevolut...tt-protocol.htm

2. http://electronicdes...2m-s-boundaries

3. http://www.layer7tec...-protocol-wars/


Is there any plan to support hot IoT device protocol such as MQTT or websocket? Or is there any specific reason to use HTTP REST in Carriots?

#2 mcastillo


    Carriots CEO

  • Administrators
  • 34 posts
  • LocationMadrid

Posted 04 June 2014 - 04:50 PM

Hi, Thanks for your feedbak . In less than 10 days, a new release will be deployed and Carriots will support MQTT. In any case there is a war between protocols for IOT and no clear winner. Based on our experience HTTP REST is the best approach. But Carriots is committed to support multiple protocols. In the meantime enjoy Carriots. Best Regards, Miguel

Also tagged with one or more of these keywords: http, websocket, protocol, mqtt

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users