KEDA requires a component which can queue messages and expose a count of how many messages are queued to trigger the autoscaler. This works for something like Kafka or ActiveMQ, but may not work for a forwarding-only architecture. (My basic understanding of MQTT implementations is that they are mostly forwarding rather than persist and then send.)
Show more
In systems where devices are expected to go offline often, like wireless sensor networks, they have do have persistence. But they're often more simple proxies that try to deliver when a device is back online, rather than a stream processing system like Kafka et al. But yes, many are proxy/caching layers too.
Show more
Aha, I take back my comment about MQTT being mostly forwarding; it sounds like most implementations are closer to publish-subscribe systems.
Show more
You're suggesting
