Blog

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.

In this blog post, we will introduce some of the improvements of the MQTT broker cluster scalability.

Early September, a few of us in the team got invited by the guys from Industry 4.0 Solutions to the Company Spotlight online event.

EMQX 5.0 has reached alpha.5 release. And we expect the first beta release to come soon.

EMQX development work is in full swing this July. We have added some exciting features and made a breakthrough progress on the key tasks of version 5.0.

Since many weeks ago, we have been working hard to define EMQX 5.0, it has been quite challenging to scope, prioritize, and finally get to focus on development in June.

Although a lot of changes originally planned for v5 have been pushed earlier to v4.3, the greater remaining work for v5 is just getting started, and everybody is so pumped to get started.

In April, EMQX 4.3-beta.5 release summed up all the fixes has to be done before 4.3.0 release. This allowed us to gradually shift our focuses towards 5.0 development.

In March, the focus of our work was on finalising 4.3 release as well as the design of EMQX Broker 5.0

To make our open source projects moving forward in a more innovative, positive, and efficient rapid iterative state, the EMQX team announced that started to officially adopt the RFC process to collect suggestions from the community and to continuously improve the product's functions.