Shulou(Shulou.com)06/01 Report--

How to carry on the ActiveMQ study of message middleware MQ, aiming at this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

MQ is mainly used in Linux to match the high availability of later services. The current technology department is so available, persistent, distributed and clustered that it is embarrassing to show up in this great people's Huaxia. Generally speaking, you will find that the usage is different, but the logic and concept are the same.

No nonsense, but also have to hand-in-hand the integration of MQ, features and other tests, but now the computer at home does not have Linux, can only write more theoretical knowledge, later on the weekend.

The release mode of MQ is mainly Queue,Topic, so let's have a brief understanding-

Queue: equivalent to synchronize, serial, one-to-one, this idea, you send me a message, first sent to the Tencent server, and then forwarded to me, my phone off, the message will not be lost.

To display detailed messages, which is equivalent to, concurrent, one-to-many, Wechat official account, your message before you subscribe is not received. When you subscribe, I post the message to the official account alone, to the server, and there are many subscribers. Then these subscribers will receive the message.

The structure of JMS: message service, which can be understood as a Http request. When you publish a message and send a request, you focus not only on the message itself, but also on the message header, message body, message properties, etc.

The role is divided into message provider (Procvider)-MQ server

Producer (Producer)-publish message client

Consumer (consumer)-consumption message

Message (message)

Although English professional nouns are not good, I can translate them. But look at this.

A good broker should be an example of MQ, and the result should be translated into 3 results. You can't simply understand if you look at the official website.

Message repeat consumption

Consumer transaction is true but not committed

After session.commit () is submitted, it is normal

Persistence of MQ

When it comes to persistence, the first thing that comes to mind is redis's persistence feature, RDB,AOF.

Physical memory is the most effective way to put messages into the database, but frequent reads and writes affect IO. When you say IO, you have to say oh, space complexity!

Cut!

Persistence of 1.0:mq

①: AMQ

②: KahaDb (default) transaction log + index

③: JDBC: MQ+MySql

④: LevelDB (starting the 5G era)

⑤: JDBCPlus (Journal) accesses journal first and then JDBC to avoid frequent read and write

2.0: highly available redis+zookeeper master-slave cluster

This is the answer to the ActiveMQ learning question about how to carry out the message middleware MQ. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.