3 ms·
In my experience MQTT works well for telemetry and one-way messaging, but it's not good at doing request-response flow like you typically do in an application u
by patwolf 6y ago
In my experience MQTT works well for telemetry and one-way messaging, but it's not good at doing request-response flow like you typically do in an application using HTTP. You can certainly come up with a mechanism for doing that, but you're having to re-invent a lot of what HTTP already solves.
- BrandoElFollito 6y agoHTTP is synchronous. MQTT is asynchronous. HTTP is 1:1. MQTT can be 1:many. What you use completely depends on your specific case.