Explain why MQTT is a good fit for RSMP #16
Conversation
| handled independently of each other. It also handles management issues since the | ||
| equipment doesn't need to keep track of communicating with several management | ||
| systems. Access control can be managed by the broker. | ||
|
|
There was a problem hiding this comment.
What do you think about adding this :
"By leveraging load balancing, MQTT could distribute the communication load across multiple brokers, potentially enhancing system performance under heavy traffic. The ability to broadcast messages to groups of devices using topic hierarchies might further optimize message delivery. These features could contribute to better management of system load and improve overall resilience, ensuring uninterrupted communication even under failure or high-demand scenarios.
graph LR;
MQTT1<--->MQTT2;
MQTT1<--->MQTT3;
MQTT2<--->MQTT3;
"
There was a problem hiding this comment.
Good idea to include a section on scalability.
There was a problem hiding this comment.
Thank you for the feedback. I've updated the draft.
|
I suggest splitting the text into somewhat smaller sections with headlines. |
|
Asist mentioned the use-case of a TLC that needs to send status updates to two different authorities, which would imply to different brokers. Perhaps we should have some diagrams showing the most common use-cases (single supervisior, multiple supervisors, multiple authorities, site-to-site, supervisor-to-supervisor, etc)? |
Initial draft of why MQTT is a good fit for RSMP