Skip to content

handle multiple mqtt server/cluster based on paho client

License

Notifications You must be signed in to change notification settings

snapp-incubator/pakhshi

Repository files navigation

pakhshi

GitHub Workflow Status GitHub Workflow Status Go Reference Codecov

Introduction

Consider you have an array of brokers but you want to publish and subscribe on all of them at the same time. Why you may need this setup? consider clients are randomly distributed between available clusters and you don't want to check which client is connected to which broker so you will publish on all cluster and your client is connected to one them.

How?

This library use paho in the background so you can easily change your applications to use this instead of paho. It trying to implement all paho interfaces.

Examples

The following example shows how to subscribe on the same topic on two brokers.

opts := mqtt.NewClientOptions()
opts.AddBroker("tcp://127.0.0.1:1883")
opts.AddBroker("tcp://127.0.0.1:1884")

c := client.NewClient(opts)

if token := c.Connect(); token.Wait() && token.Error() != nil {
  assert.NoError(t, token.Error())
}

if token := c.Subscribe("hello", 0, func(c mqtt.Client, m mqtt.Message) {
  ch <- string(m.Payload())
}); token.Wait() && token.Error() != nil {
  assert.NoError(t, token.Error())
}

Credits

Based on idea of Ahmad Anvari.

About

handle multiple mqtt server/cluster based on paho client

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages