MQTT is a publish/subscribe protocol. Whenever a publisher publishes to a topic, all the subscribers that have subscribed to that topic will get the message via an MQTT broker. I would like to know the maximum number of clients an MQTT broker can handle. Is there any upper limit for that?
相关问题
- Why use MQTT Node.JS library?
- AWS store MQTT message to DynamoDB
- JavaScript client for MQTT not using WebSockets
- Paho MQTT Python Client: No exceptions thrown, jus
- mqtt on Laravel with PHP
相关文章
- Connecting Unity3d Android application to ActiveMQ
- Integrating MQTT with GCP using IOT adapter and go
- How can i connect a Java mqtt client with username
- How to build a system to handle MQTT broker and Dj
- How to send a jms message to activeMQ and decode i
- golang mqtt publish and subscribe
- MQTT over websocket in python
- MQTT-Client-Framework stay running at background
The only way to work this out is to test depending on your specific workload.
It will be entirely dependent on the following:
And possibly many more factors.
How many clients an MQTT broker can serve depends on the MQTT broker software you're using. Most MQTT brokers will likely only be limited by the amount of memory available (each socket uses a chunk of memory) and it therefore becomes a question of which broker software utilizes the memory (and other resources) in the most efficient manner. Of course some brokers might have other limitations.
In practice you'd also have to look at what you can do with the connected clients - some brokers may behave differently (performance wise) depending on how many clients are connected etc.