4

So, I have a bunch of mobile devices (millions) and will have a backend system. My needs/use case are:- 1. To collect data from the devices and send to backend. 2. To send Push messages from my backend system to individual or groups of devices.

So, given this scenario, does it make sense to use MQTT for communication between my backend and the devices? One of the confusions, that I have is that in use case #1, devices are publishers and some system in backend will be subscribers, whereas for use case #2, devices are subscribers for the push messages and a backend system will be the publisher. Is this possible? Or am I thinking about it the wrong way?

Praveen Thirukonda
  • 365
  • 1
  • 4
  • 16
  • 1
    Your requirements have been well documented in chapter 5 of MQTT Redbook: http://www.redbooks.ibm.com/redbooks/pdfs/sg248054.pdf – Shashi Aug 20 '13 at 04:26
  • @Shashi Thanks so much for the link to the book. This is very useful and good information. I am surprised I did not find the book earlier as I have been researching on MQTT for past few days, guess it must have been buried deep or I need to brush up on my Google-fu skills :-) – Praveen Thirukonda Aug 21 '13 at 15:32
  • @Shashi Could I ask where you originally found the link to that book? I mean is it to be found on some IBM page on MQTT? – Praveen Thirukonda Aug 21 '13 at 17:11
  • The first hit on a Google search with "mqtt redbook" keywords will take you to the MQTT Redbook. – Shashi Aug 22 '13 at 05:03
  • Oh, OK. I just didn't know that something like a RedBook exists. Thanks, anyways. – Praveen Thirukonda Aug 22 '13 at 17:02

2 Answers2

3

Having worked on a number of examples (e.g. a mobile telemetry system with push notification) that fit this usage pattern I can say that MQTT can fit perfectly. Any MQTT client can act as both a publisher and a consumer, there is no distinction.

You will just need to design your topic structure to suit the data you are sending in either direction, but that should not be difficult.

hardillb
  • 54,545
  • 11
  • 67
  • 105
1

In general, MQTT is a perfect fit for your use case #1 and use case #2.

Please keep in mind that you will probably get problems at this scale with backend subscribers because there are (as far as I know) no MQTT libraries around which can handle such a massive throughput.

A slightly different approach would be that the broker communicates directly with the backend, analogous to this blog post

Here is an interesting discussion on the MQTT mailing list on this topic.

Dominik Obermaier
  • 5,610
  • 4
  • 34
  • 45