Speaking of the topic of MQTT for, uh, it is actually like integrating the old system. MQTT is a lightweight, publish/subscribe mode message transmission protocol, which adopts this method when transmitting data on the network. You see, communication and integration of some old systems are quite troublesome. But with MQTT, integration in old systems can bring many benefits.
Let’s first talk about why I chose MQTT. First, its overhead is extremely low. After all, some old systems are not very good in performance. If you choose a protocol that takes up resources, it will be too heavy to the system. But MQTT is lightweight and does not occupy many valuable resources. For example, when some production monitoring systems built ten years ago have limited hardware and software resources, it is feasible to introduce the MQTT protocol at this time.
Secondly, it can be quite suitable for low bandwidth and unstable network connections. Many old systems deploy geographical locations and these networks are not well-deserved, which are worse than those in remote areas, which are difficult to transmit data. MQTT has a special mechanism to solve such problems. There is also a basic security guarantee, although let’s briefly talk about it. What can be authenticated based on the lightweight TSL/TLQ protocol?
Let’s talk about the specific role reflected in the application-level scenario. On the one hand, it can achieve real-time data communication. Different old systems are scattered, and it is difficult for information to flow and flow between systems to spread. After MQTT builds message communication middleware, each system only needs to connect MQTT to publish or subscribe, and the information is transmitted very quickly. For example, the inventory management of an old warehouse needs to transmit data. The inventory update can be completed quickly in the logistics hub.
Let’s talk about the details and details of the module classification. First of all, if the old system cannot provide a suitable data interface, is it MQTT solution? In fact, there is a way to use the hardware converter hardware. This converter is useful when the old system sensor is connected to the MQTT application. For example, it can be used to convert the serial port to the network MQTT connection form, or to use other protocol data from the network data signals, etc. Some old system applications are not active in maintaining their own system, and at this time, they can use the converter to collect appropriate data for MQQT.
When it comes to the protocol conversion, there are many old traditional private protocols. Faced with this situation, you can write special software modules. This process of transition between private agreements and public employment agreements such as MQQT can be reached. For example, some industrial control systems used to communicate based on protocols and then docked to MQQT for special module processing.
After this part, I will tell you the Q&A part
Someone asked MQTT for legacy system integration, why should I prioritize MQQT without HTTP protocols for old system integration? Let's say that, although HTTP is widely known to everyone, HTTP has no connection characteristics. It is object-oriented. After interaction, it can be used to synchronize data continuously and continuously. There is no way to use MQQT. Continuous connection and publishing push modes. The data is more feasible.
Some people also say, if many old systems of different manufacturers are placed together and integrated with MQTT, how to coordinate communication? This can be solved by MQTT with a theme mechanism function. The theme mechanism is similar to a folder. Set the respective theme identification system to transfer data according to the theme specifications.
Then, some people are worried that the old system itself is not reliable in its security factor and the risk of MQQT? Actually, it's okay because MQQT has a session-keeping function mechanism. Once communication is interrupted, the messages can be cached and stored until the next time they connect, and then resume work and continue work. In addition, the lightweight and authentication mechanism is safe and secure.
Okay, let’s talk about the comparison questions. Let’s compare other traditional transmission protocols. For example, when HTTP is integrated in this type of integration, it is not good to have complex processes and real-time synchronization; but MQTT is simple, convenient, real-time and easy to use. The CORBA system interface is too complex to build, and the MQTT interface is simple.
Regarding security, I just said it is basically very simple. It just skipped the security angle. Although MQTT is lightweight, it has made many measures using the appropriate transmission layer TLS and combined with the security mechanism of the customer's own control center, it has also been effectively integrated and coordinated.
Provide global procurement services for weak current intelligent products!
Well, I think this is how I think about it. Ha, the integration of the old system is pretty good. It really solves many practical problems. Although new technologies are constantly changing, MQTT can save too much manpower, economic time and resources in terms of operation and maintenance, so the promotion should be more extensive and better. Therefore, no matter whether it is resource saving or actual results, it must be allowed to play a greater role in the future to be particularly useful in our traditional old enterprise field.
Leave a Reply