MQ and MB

Today, I heard from IBM engineers about the features of MQ and MB, as well as their differences and connections. I think it is easy to understand, this makes it easier for future beginners to grasp the features of both.

In terms of concept, MQ is a message-oriented middleware and MB is an ESB product.

MQ is responsible for transmitting messages between two systems. These two systems can be heterogeneous, in different hardware, operating systems, and written in different languages. Only a few MQ APIs need to be called, you can communicate with each other without considering the complexity of the underlying system and network. As a fist product of IBM, MQ seems simple as a message queue, but it is the core of IBM middleware and an advantage over other vendors (such as BEA. MQ not only has high performance, but also supports a variety of platforms very well. You can think of the hardware and operating system platforms andProgramming LanguageAnd MQ all have dedicated API support.

However, the MQ function is limited to message queues. As for how the message format sent by application a to application B can be parsed by application B, MQ cannot manage it, he only tries his best to send messages to the destination (MQ can cope with various exceptions, such as network congestion and temporary interruptions ). In addition, if the number of applications is large, MQ connections must be established between each other, and the network topology becomes a Spider Network (like the original telephone system)

Therefore, we introduce the star topology of the network into the system architecture, and replace one-to-one MQ with a central node, that is, ESB, and MB is the ibm esb product.

MB is at the center of the system and acts as a bus. All applications are directly connected to MB instead of directly interconnected between applications. This advantage is self-evident and can greatly reduce the coupling between applications. The two core functions of MB are introduced as follows: message routing and data conversion.
Because each application is inserted to MB, application a only throws the message to MB. MB automatically determines who to send the message based on the message field and business logic, like a router, this route the packet to the corresponding address based on the packet header. The internal business logic of MB is set by developers. Of course, using the toolkit of MB, writing business logic is also very simple: drag some nodes and connect them with arrows, just like drawing a flowchart, simple image. Use MB script language (similarSQL(If... else .....).

But how are applications connected to MB? MB provides three methods: MQ, file, andWebService

The MQ method uses MQ to interconnect MB with applications. The file method specifies a directory, and MB automatically monitors the file directory. Once the file changes, it is considered as a new message, MB automatically reads the content of the specified file, and the Web service does not need to be explained. The Web Service is used for communication directly. MB supports these interconnection modes to maximize compatibility, especially for legacy systems or systems that do not support mainstream communication modes.

Finally, let's talk about a relatively biased ESB product:WebSphereESB. Not many people have heard of it, Because IBMChinaThis wesb is very similar to the MB Lite version. It only supports a few J2EE communication methods such as JMS and WS, so it is specially prepared for J2EE. Unlike MB, it supports dozens of platforms and communication methods, such as FTP, and even many old communication protocols that you have never heard. The performance of the two is quite different, and the price is also three or four times different. What's even worse is that what was originally developed on wesb cannot be migrated to MB. IBM seems to be eager to kill us. The only way is to buy another MB, then we use MQ to connect wesb and MB, and each of them runs separately.

A datapower is missing. I only know about this. The selling point is that the hardware supports XML, so the performance is better. In addition, it also supports Web Service Security. Therefore, wesb is the smallest feature set, while MB and datapower overlap functions, such as XML

Finally, I am not advertising to IBM