This discussion is locked.
You cannot post a reply to this discussion. If you have a question start a new discussion

I am the vice-chair of the IOT Committee, at the IET. I would appreciate a bit of help please. MQTT & HTTP.

I am the vice-chair of the IOT Committee, at the IET. I am needing a bit of help please.


Does anyone have a short summary document which explains which type of “use case” is more aligned to MQTT, and which is better for HTTP?  I have been searching “everywhere”.  Most things I find are “out of date”, or written by someone who works for a company which has a commercial position – which benefits from either MQTT or HTTP. i.e. they are biased. 


Ideally, I am looking for a purely research paper, or something written by an academic. Or something ad-hoc, written by a networking person who understands this. 


Note. To date, I have found only one independent source, written by a student. He includes lots of formulae (way above my academic level) and he explains his test environment, and I am OK with that. I am using his paper as the basis for my understanding. But, after a week of searching, that is the only independent document I can find.


I have done quite a bit of research, and found what are described as independent studies. These come from very large companies. But when I research what they say, …. I find holes.  


My problem is that I am only “average technically”, and I cover a very wide range of technologies. I am also a sales person, in my job-role. So, I just cannot be as “good” as someone who does this as part of their normal job.


I am due to give a 15 minute presentation about this on Tuesday, to quite a prestigious group of “internet engineers”. This is in my other voluntary role, which is aligned to the UK Military and the IoT. (I am ex Royal Signals).


In terms of my employer, this is who we are; Eurotech, see https://www.eurotech.com/en

Our products support both HTTP and MQTT. We do not charge money for either. In fact most of our key technologies are donated to the Eclipse Opensource foundation, Our IoT Gateway Client is donated as KURA, and our IoT Cloud Component as KAPUA. Please see; https://www.eclipse.org/kura/ and  https://www.eclipse.org/kapua/  


Anything appreciated.

Mike
mmckean917@gmail.com

Or
michael.mckean@eurotech.com




  • By my little bit of understanding, http is a markup/formatting language for web pages, whilst mqtt is a compact and human readable protocol for passing small bits of data across the web from point to point, things like temperature and humidity. Therefore mqtt is interesting for me, whilst http is only of marginal interest.
  • MQTT is built around a publisher/subscriber model - your fish pond sensor publishes temperature and oxygen content figures to a host website such as AWS, and your smartphone subscribes to these parameters, a bit like a newsletter.
  • Hi Alex, many thanks. Mike