MQTT

You can use ReductStore to keep a history of MQTT messages by using its Client SDKs. This can be useful if you use a binary format for your data and it can be recorded in a classical TSDB. You can set a FIFO quota for a bucket in your ReductStore instance so that the database removes old MQTT messages when the limit is reached.

Hi All,

I'm looking to develop an ESP32-based local (that is the hub is on the same network) and small (usually no more than 10 devices per hub) IoT network over wifi.

For Most of the runtime, the devices report readings with max 1s frequency to the hub, and MQTT is great for this. But I'm looking for future needs such as FOTA, and maybe some RPC on the devices. MQTT can be used to execute functions (with the result reported on another topic) on the edge devices but it feels hacky and wrong long term.

I've looked at various IoT frameworks, but many are paid which is a non-starter or seems like overkill (like a cloud backend for millions of devices). I'm looking for the best tools for a small device network, running on a local resource-constrained Linux.

I'm hoping for open-ended feedback or some library recommendations for further reading, Many thanks in advance!

Hi Marc,

For the com part, depending of more details not provided, i'd use SSE, OR i'd run either Mosquitto or RabbitMQ running on Amazon EC2 instances and leverage MQTT or amqp 's subscribe/publish features with my users running mqtt or amqp clients (tcp or websockets) somehow. (publisher too.. you don't say how and who gets to update the document(s).

I find "a ton of end users", depending on how you define a ton (1k users ;) ?) and how frequent document updates are, that can mean a ton of ressources, can't cut it at some point, even using SSE

how many, how big, how persistant do the document(s) have to be ? Db-wise,can't say for lack of details and context, yeah could also be Redis, any RDBMS or nosql or even static json files stored on an Amazon S3 bucket .. anything really

Good luck!

Kindly suggest the best tool for generating 10Mn+ concurrent user load. The tool must support MQTT traffic, REST API, support to interfaces such as Kafka, websockets, persistence HTTP connection, auth type support to assess the support /coverage.

The tool can be integrated into CI pipelines like Azure Pipelines, GitHub, and Jenkins.

I want to use NATS for my IoT Platform and replace it instead of the MQTT broker. is there any preferred added value to do that?

MQTT is one of the light weigh, its small size, low power usage, minimized data packets and ease of implementation make the protocol ideal of the “machine-to-machine” or “Internet of Things” world. we have used it to communicate with devices from server.