https://github.com/1995parham-learning/mqtt101

Learn MQTT and some other related technologies
https://github.com/1995parham-learning/mqtt101

golang mqtt paho-mqtt

Last synced: about 2 months ago
JSON representation

Learn MQTT and some other related technologies

• Host: GitHub
• URL: https://github.com/1995parham-learning/mqtt101
• Owner: 1995parham-learning
• Created: 2020-04-18T16:45:20.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2023-11-17T16:42:24.000Z (about 1 year ago)
• Last Synced: 2024-06-22T15:50:51.515Z (7 months ago)
• Topics: golang, mqtt, paho-mqtt
• Language: Go
• Homepage:
• Size: 69.3 KB
• Stars: 4
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
MQTT 101



  




## Introduction

Technologies like CoAP or MQTT are known to be useful in the field of IoT, but in the today world

you can use them for any type of communication with your clients, so they are really important and useful.

MQTT protocol is supported on wide variety of devices from Android Smartphones to Linux servers that are placed in

datacenters. MQTT protocol has two sides, consumer and the producer and both sides are simple and easy to implement.

The hardest part is implementing the broker that handles the connection between producers and consumers.

I've worked with [EMQX](https://vernemq.com/) and [VerneMQ](https://vernemq.com/) as brokers and both of them are awesome.

In this repository we implement consumer and producer for MQTT protocol with Golang based on Paho library from Eclipse.

## Implementation

The pure Go implementation of mqtt protocol is available from [paho.mqtt.golang](https://github.com/eclipse/paho.mqtt.golang).

The following code grabbed from the library and shows that the given on-connect handler runs on another go routine.

```go

c.setConnected(connected)

DEBUG.Println(CLI, "client is connected/reconnected")

if c.options.OnConnect != nil {

 go c.options.OnConnect(c)

}

```

This implementation works great, and you must not forget to re-subscribe on connection lost

To this just do subscribe with on-connect.

## Deployment

As you may guess, the hardest problem after writing the first MQTT application is deploying the Broker.

I've chosen EMQ here because of its performance.

At [AoLab](https://github.com/AoLab) Iman and I deployed it with default configuration on a small (4G, 4 cores) virtual machine,

and it handled 1000 concurrent connections without any issue.

Now, we want to deploy it on cloud, and we want to use its [official chart](https://github.com/emqx/emqx/tree/master/deploy/charts).

On the production, you must pay attention to security and performance.

For security, you can choose between different methods of authentication and authorization, which are provided by EMQ.

The most flexible option is using HTTP authentication because you can write whatever you want on your HTTP server.

```bash

helm repo add emqx https://repos.emqx.io/charts

helm dependency build

helm install emqx . -f values.yaml

```