EMQ X broker is a fully open source, highly scalable, highly available distributed MQTT messaging broker for IoT, M2M and Mobile applications that can handle tens of millions of concurrent clients.
Starting from 3.0 release, EMQ X broker fully supports MQTT V5.0 protocol specifications and backward compatible with MQTT V3.1 and V3.1.1, as well as other communication protocols such as MQTT-SN, CoAP, LwM2M, WebSocket and STOMP. The 3.0 release of the EMQ X broker can scaled to 10+ million concurrent MQTT connections on one cluster.
#github #emqx #mqtt #pubsub #wss #ws #websocket #web_socket
Starting from 3.0 release, EMQ X broker fully supports MQTT V5.0 protocol specifications and backward compatible with MQTT V3.1 and V3.1.1, as well as other communication protocols such as MQTT-SN, CoAP, LwM2M, WebSocket and STOMP. The 3.0 release of the EMQ X broker can scaled to 10+ million concurrent MQTT connections on one cluster.
https://github.com/emqx/emqx
#github #emqx #mqtt #pubsub #wss #ws #websocket #web_socket
Caddy
is the HTTP/2 web server with automatic HTTPS. I wanted to proxy pass websocket service using Caddy
but it didn't work:wss.example.org {
proxy / myservice:8083 {
header_upstream Host {host}
header_upstream X-Real-IP {remote}
}
tls myemail@gmail.com
}
In the documentation it is mentioned that
proxy
can proxy pass web sockets too. The problem was about not using websocket
inside of the proxy stanza, so we solved it using:wss.example.org {
proxy / myservice:8083 {
header_upstream Host {host}
header_upstream X-Real-IP {remote}
websocket
}
tls myemail@gmail.com
}
#webserver #caddy #proxy #proxy_pass #wss #ws #websocket