Hi there, mind sharing some insights about your backend, available GEO Locations & latency? Also, I am not going to create an IoT App, but frequently run into situations where I would prefer using e.g. PubSubHubbub (aka WebSubHub) but simply don't want to run my own nor want to rely on e.g. Google for it - which I currently do & living at their mercy about the future of the related services.
My main use case is getting an edge on udpated xml feeds where knowing just a few minutes earlier than the average Joe is crucial (e.g. I monitor SEC GOV filings streamed for publishing but not yet pushed to mainstream feeds which then by themselve only poll every x Minutes if not hours later.
Not sure if this kinda makes sense to you, so my main question remains as initially asked above in order for getting an idea how you fit in.
A: The MQTT Broker is a self hostable and can be run on any cloud provider or even on premise. As stated, you can keep it very close to your location to make sure you are compliant with your data security requirements. MQTT Broker is standalone and does not use any cloud provider application and at the same time flexible to integrate.
On the latency, A single instance of the MQTT Broker can give you a data exchange rate of more than 1 MB / second and can peak to 2 to 2.5 MB/second based on the network conditions.
On the XML file exchange, the Broker supports Binary ( Non UTF ) as well. However, The overall architecture need to be understood before anyswer your question.
Streaming Source ( Publisher) --- > MQTT Broker ---- > Your IoT App or the receiver app.
How are the other two pieces hosted and the connectivity to be understood before we can comment on the implementation.
Hope this answers your query. Correct me if my understanding is wrong.
Q: Qs around BackEnd, Latency, ...
Hi there, mind sharing some insights about your backend, available GEO Locations & latency?
Also, I am not going to create an IoT App, but frequently run into situations where I would prefer using e.g. PubSubHubbub (aka WebSubHub) but simply don't want to run my own nor want to rely on e.g. Google for it - which I currently do & living at their mercy about the future of the related services.
My main use case is getting an edge on udpated xml feeds where knowing just a few minutes earlier than the average Joe is crucial (e.g. I monitor SEC GOV filings streamed for publishing but not yet pushed to mainstream feeds which then by themselve only poll every x Minutes if not hours later.
Not sure if this kinda makes sense to you, so my main question remains as initially asked above in order for getting an idea how you fit in.
Ranjith_MQTTBroker
Apr 21, 2025A: The MQTT Broker is a self hostable and can be run on any cloud provider or even on premise. As stated, you can keep it very close to your location to make sure you are compliant with your data security requirements. MQTT Broker is standalone and does not use any cloud provider application and at the same time flexible to integrate.
On the latency, A single instance of the MQTT Broker can give you a data exchange rate of more than 1 MB / second and can peak to 2 to 2.5 MB/second based on the network conditions.
On the XML file exchange, the Broker supports Binary ( Non UTF ) as well. However, The overall architecture need to be understood before anyswer your question.
Streaming Source ( Publisher) --- > MQTT Broker ---- > Your IoT App or the receiver app.
How are the other two pieces hosted and the connectivity to be understood before we can comment on the implementation.
Hope this answers your query. Correct me if my understanding is wrong.
Thank you,
Ranjith
Share MQTT Broker
Got ya. Didn't realize its selfhosted.