mosquitto-users team mailing list archive

[Eurig Jones <eurigjones@xxxxxxxxx>]

Hey,

I'm looking into Mosquito as a back-end for a push notification system that
would be designed to scale well to support 2 or 3 million concurrent users.
For the clients (mobile devices) the service would be read only and
authenticated. For a single client (the server that sends the messages to
the MQTT) it would be read/write.

I'm thinking that there could be a topic for each device connected to the
server, as I can't envisage us ever having multiple clients subscribed to
the same topic. Basically it's a "one(client) to many" style of
communication.

My questions are (for the Mosquito implementation of MQTT specifically):
- Is it a good idea to have this style model in terms of performance and
resources?
- Is there a better way of doing this?
- Does a topic have a large footprint?
- Will it take time for the broker to find a topic if there are millions in
its database?

Thanks
Eurig