EMQX Cloud (Pay as you go)

EMQX  is a unified architecture and unified namespace based on MQTT broker, primarily using EMQX  or HiveMQ. We use EMQX for the communication of factory data, sensors, and PLCs.

We track data on sensors and MQTT data by collecting MQTT data for sensors and publishing it to the MQTT broker. We then fetch MQTT data again, calculate some KPIs, and publish these KPIs back to the MQTT broker.

We primarily use energy data for reducing energy costs and calculate the machine state of machines. We use EMQX and MQTT mostly for the machine state of machines. We collect machine data, such as temperature or pressure and sensor values in machines, and then calculate the machine state of the machines or lines. We collect energy data of these machines in energy analyzers and calculate the total energy of the products.

The best features EMQX offers include fast communication; MQTT is the fastest protocol that I have observed.

MQTT scalability is excellent, and I am using the REST protocol. The REST protocol is not scalable as it is an old protocol, but MQTT runs a pub-sub mechanism and it is very fast and very scalable. This is excellent.

MQTT enables us to use unified namespace architecture. I collect data and publish data to MQTT and use this factory data on the MQTT broker. This enables us to have very fast integrations and data integrations, and I see data when I need it very quickly. When I use the MQTT broker, I do not need a database. EMQX broker is unified.

For example, MQTT 5.0 is a new version that is very fast.

EMQX is a good MQTT broker but the historian is simple. The historian side of EMQX and MQTT is simple and could be better.

It could be more reliable in new versions.

I have been working in my current field for three years.

EMQX is very stable in my experience.

EMQX's scalability is excellent and I have used EMQX for very big data and it is a very scalable solution.

When I need any support, I read forums and there are many articles in forums.

We were using a database, for example, MSSQL  or PostgreSQL . In my old experience before MQTT, MQTT is faster than database solutions and more lightweight solutions.

I have seen a return on investment with money saved and time saved because the protocol is MQTT.

EMQX is an open-source protocol. The cost is mostly the cloud provider cost. EMQX is open-source and MQTT is also an open-source protocol, so the cost is less.

I evaluated other options before choosing EMQX.

EMQX is a unified namespace architecture and is a lightweight solution compared to old database solutions such as MSSQL  or PostgreSQL . EMQX is also a very fast communication protocol. MQTT is a very fast communication protocol.

I appreciate EMQX as it is a very lightweight solution. This review has an overall rating of 8.

My main use case for EMQX  is for communicating with ESP32 devices and sharing messages from one device to another device at the central level.

Our company is a fuel automation company, and we will have dispenser units where we connect one ESP32 for each dispenser unit. We get all the data from the dispenser unit and share it to the server via EMQX .

One of the best features EMQX offers is the ability to share data via topic-wise distribution.

Topic-wise data sharing helps my team and our workflow because each ESP32 has a different MAC ID, and using the MAC ID, we filter the data in the server, determining which ESP32 sends which message for a particular dispenser unit.

I would like to add that we are using TLS security for EMQX, and we have created one server where we can use a certificate for security purposes. The speed is really high, and even if there is a large number of incoming data, EMQX handles it very smoothly and quickly.

EMQX has positively impacted our organization by significantly increasing speed compared to other technologies we used before. After using EMQX, we can now handle a large amount of data within a fraction of seconds, which makes it very easy for us to pass the data and store it in our database, and we can easily visualize it in our UI.

The outcomes from using EMQX are very cost-saving for us because we previously used the MQTT Mosquitto broker, and when I compare Mosquitto with EMQX, EMQX is far better than Mosquitto and other protocols.

I do not have any suggestions for improvement in EMQX.

As I have worked with EMQX, I do not feel much improvement is needed. Whatever is available till now is working great and is very efficient for us. Perhaps I need to explore more to add new features or other functionalities, but as of now, it is great for us.

I have been using EMQX for 14 months.

EMQX is much more stable.

EMQX's scalability is really great.

We have not faced any need for customer support from EMQX since we can handle everything on our end.

We previously used the Mosquitto broker, which had latency issues and could not handle a large amount of data, and it was very slow. That is why we searched for an alternative option and found that EMQX is better.

We have not deployed EMQX to a large extent yet, so I cannot provide specific metrics, but we are optimistic about the return on investment.

My experience with pricing, setup cost, and licensing for EMQX is good.

Before choosing EMQX, we evaluated other options, including HiveMQ.

My advice for others looking into using EMQX is that if they want to manage a large amount of data with more speed, reliability, and security, they can easily switch to EMQX compared to other brokers. I give EMQX a rating of 10.