Introduction to MB and MQ

Today, IBM engineers introduced the MQ and MB features, and their differences and connections, feel very easy to understand, it is recorded, so that future beginners can quickly grasp the characteristics of both.

First, conceptually, MQ is the message middleware, and MB is the ESB product

MQ is responsible for passing messages between the two systems, the two systems can be heterogeneous, in different hardware, different operating systems, written in different languages, simply call a few MQ APIs, you can communicate with each other, you do not have to consider the complexity of the underlying system and network. As an IBM blockbuster, MQ, while seemingly simple, is a message queue, is at the heart of IBM middleware and an advantage over other vendors such as Bea. MQ has not only high performance, but also very good support for various platforms, and almost all of the hardware and operating system platforms you can think of, as well as the programming language, MQ has dedicated API support.

But MQ's function is limited to Message Queuing, as to how the message format of application A to application B can be applied B parsing, MQ does not, he just tries to send the message to the destination (MQ can handle a variety of abnormal situations, such as network congestion, temporary interrupts, etc.). In addition, if the number of applications is more, then each other to establish an MQ connection, the network topology becomes a spider web (it is like the initial telephone system)

Therefore, we introduce the star topology of the network into the system architecture, and replace the one-on MQ with a central node, that is, ESB,MB is IBM's ESB product.

MB in the center of the system, play a role in the bus, all applications are directly connected to the MB, rather than the direct interconnection between applications, the benefits are self-evident, can greatly reduce the coupling between applications. This leads to two core functions of MB: Message Routing and Data conversion

Because each app is plugged into megabytes, apply a just drop the message to MB,MB automatically according to the Message field, as well as the business logic, to determine who to give the message to whom, like a router, according to the packet header packets to the corresponding address. MB internal business logic is set by the developer, of course, the use of MB toolkit, writing business logic is also very simple: drag some nodes, with arrows to connect them, like a flowchart, very simple image. Then use the MB scripting language (SQL-like script) to achieve logical judgment, popularly speaking is to decide which logical branch to go (If...else ... ）。

But how does each application connect to the MB? MB is available in three ways: MQ, file, and Web service

MQ is the use of MQ to connect MB with the application, file mode is to specify a directory, MB will automatically monitor that file directory, once the file changes are considered to be a new message arrives, MB automatically read the contents of the specified file, and the Web service does not need to explain, directly using the Web Service for communication. MB supports these interconnects in order to maximize compatibility, especially for systems that have legacy systems or that do not support mainstream communications

Finally, say a more biased ESB product: WebSphere ESB. People may not have heard much, because IBM in China to promote a relatively small, this wesb is very similar to a compact version of MB, only support JMS, WS and a few other types of Java EE communication, so it is specially prepared for the Java EE. Unlike MB, it supports dozens of platforms and modes of communication, such as FTP, and even a lot of old communication protocols that you never heard of. The performance difference between the two, the price also has three or four times times the gap. What's more, originally developed on the WESB, is not migrated to MB use, IBM seems to iron heart to kill us, the only way is to buy another MB, and then use MQ to connect Wesb and MB, each run the

Missed a datapower, this thing I just slightly understand, its selling point is that the hardware support XML, so the performance is better, but also support the Web service security aspects. Therefore, WESB is the smallest feature set, and MB has some overlap with datapower functionality, such as XML

Last statement, I'm not advertising to IBM.

This article is from the "6250022" blog, please be sure to keep this source http://6260022.blog.51cto.com/6250022/1739784

Introduction to MB and MQ