This article will describe in detail the new underlying architecture that exponentially improves EMQX's horizontal scalability, helping you understand the technical principles of EMQX 5.0 cluster expansion.
EMQX v5.0 has been verified in test scenarios to scale to 100 million concurrent device connections, which is a critically important milestone for IoT designers.
In May, EMQX 5.0.0-rc.3 and rc.4 were consecutively released. The updated versions now provide additional support for jq syntax to the rule engine, and a further adjusted and optimized Dashboard menu bar.
In April, the EMQX team released many maintenance versions of 4.x, which brought a number of new features on the basis of further improved stability.
This post will spotlight some of the EMQX MQTT broker features we've released through the Dashboard UI.
To stress test the scalability of the MQTT broker EMQX, we established 100M MQTT connections to the clusters of 23 EMQX nodes to see how EMQX performs.
In March, the EMQX team brought to the community the long-expected EMQX v5.0.0-rc.1.
As a MQTT broker admin, you may often want to know which clients are the slowest. We have a nice ‘top’ view for you.
In this post, we describe some of the challenges we encountered while adapting a big project like EMQX to be built with Mix.
By the end of January, EMQX team managed to reach 100 million unique wildcard subscribers in a 22-nodes EMQX 5.0 cluster.
In November, EMQX teams kept optimizing the product in response to recent problems and user feedback.
In October, EMQX development teams have been mostly focusing on HTTP management API, the readiness of which will be checkpoint for the beta.2 release.