1. 10
  1.  

  2. 5

    I took a similar road two years ago after swapping HTTP + SSE by Websockets using Erlang’s cowboy. Being able to publish and suscribe and topics gives you a better place where to start than Websockets. My main issue with MQTT was developers don’t want to deal with other protocol apart from HTTP.

    If you have some time I recommend that you check the best Erlang MQTT broker I know: VerneMQ. You can easily create clusters that deal with network partitions.

    1. 4

      My main issue with MQTT was developers don’t want to deal with other protocol apart from HTTP.

      I have a new service I will be launching sometime in the new year, and I am wanting to promote IPv6 by having two ways to get premium access: 1) Charge a monthly fee 2) Have folks connect to the site over IPv6. All they’d have to do to “pay” for the service is login via IPv6 at least once a month, and their account would be accessible from IPv4 as well.

      Perhaps this strategy or something similar might encourage adoption of MQTT as well?

      1. 1

        Thank you for the recommendation. We’re doing something similar too and we’re reaching the limits of Mosquitto as it doesn’t have support for clusters.