You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I'm working on developing an edge analytics gateway and there are multiple events streams which are intended to publish events into different MQTT topics.
When using Siddhi MQTT sinks for event publishing, a sink is defined for every output stream with the relevant topic. Then, a new MQTT connection is created for each sink, that means for each event stream, new MQTT connection is created.
This can be an issue as the number of devices connected to edge gateways are increased, as there will be large number of MQTT clients which are needed to be handled by a single message broker.
The problem can be solved if there is an ability to share a single MQTT connection between multiple MQTT sinks.
Suggested Labels:
NewFeature
The text was updated successfully, but these errors were encountered:
Description:
I'm working on developing an edge analytics gateway and there are multiple events streams which are intended to publish events into different MQTT topics.
When using Siddhi MQTT sinks for event publishing, a sink is defined for every output stream with the relevant topic. Then, a new MQTT connection is created for each sink, that means for each event stream, new MQTT connection is created.
This can be an issue as the number of devices connected to edge gateways are increased, as there will be large number of MQTT clients which are needed to be handled by a single message broker.
The problem can be solved if there is an ability to share a single MQTT connection between multiple MQTT sinks.
Suggested Labels:
NewFeature
The text was updated successfully, but these errors were encountered: