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

This article mainly talks about "what is the method of RocketMQ foundation and environment integration in micro-service architecture design". Interested friends may wish to have a look at it. The method introduced in this paper is simple, fast and practical. Next, let the editor take you to learn "what is the method of micro-service architecture design RocketMQ foundation and environment integration?"

Overview & Type selection

As one of the core components of high concurrency system, message queue can help business system deconstruction to improve development efficiency and system stability. It is mainly used in three typical scenarios: application decoupling, traffic de-peaking, and message distribution.

At present, the mainstream MQ is mainly Rocketmq, kafka and Rabbitmq,Rocketmq. Compared with Rabbitmq and kafka, Rabbitmq,Rocketmq has the following main advantages:

Support for transactional messages (message sending and DB operations maintain the final consistency between the two parties, rabbitmq and kafka do not support)

Support ultimate data consistency between multiple systems combined with rocketmq (multi-party transaction, two-party transaction is the premise)

Supports 18 levels of delayed messages (not supported by rabbitmq and kafka)

Support the retransmission of failed messages for specified times and time intervals (not supported by kafka, rabbitmq requires manual confirmation)

Support tag filtering on the client side to reduce unnecessary network traffic (not supported by rabbitmq and kafka)

Support for repeated consumption (not supported by rabbitmq, supported by kafka)

Stand-alone installation configuration

If you want to do a good job, you must first sharpen its tools. If you want to have an in-depth understanding of RocketMQ, you must first install the environment. Let's start the installation of a stand-alone version of RocketMQ!

Decompression and installation

Unzip rocketmq-all-4.7.0-bin-release.zip

Start Name Server

> nohup sh bin/mqnamesrv &

View the Name Server startup log

> tail-f ~ / logs/rocketmqlogs/namesrv.log

Start Broker Server

> nohup sh bin/mqbroker-n localhost:9876 &

View the Broker Server startup log

> tail-f ~ / logs/rocketmqlogs/broker.log

It is very easy to install and use RocketMQ in the case of a single machine, just start NameServer and Broker Server respectively.

To turn off RockerMQ, use the following command:

# close Broker Server first

> sh bin/mqshutdown broker

# shut down NameServer again

> sh bin/mqshutdown namesrv

Dual master-slave high availability building

To eliminate stand-alone failures, increase reliability, or increase throughput, you can deploy multiple NameServer and Broker on multiple servers, and one or more Slave for each Broker. This section describes the use of two machines to build a high-availability RocketMQ cluster with dual masters, double slaves and no single point of failure. Suppose you now have two servers with the IP addresses of 192.168.100.43 and 192.168.100.44, and the deployment architecture is as follows:

Start multiple NameServer and Broker

First, we need to start NameServer (nohup sh bin/mqnamesrv &) on both servers, so we have a single-point NameServer service with addresses of 192.168.100.43 and 192.168.100.44.

Then create two files broker-master.properties,broker-slave.properties in the conf directory of RocketMQ on the two servers. Here are the configuration instructions for different servers:

Broker-master.properties file on the 192.168.100.43 machine:

NamesrvAddr = 192.168.100.43 04fileReservedTime 9876 Taiwan 192.168.100.44 0deleteWhen 9876 brokerClusterName = DefaultClusterbrokerName = broker-abrokerId = 0deleteWhen = 48brokerRole = SYNC_MASTERflushDiskType = ASYNC_FLUSHlistenPort = 10911storePathRootDir = / app/rocketmq/store-a

Broker-slave.properties file on the 192.168.100.43 machine:

NamesrvAddr = 192.168.100.43 04fileReservedTime 9876 Taiwan 192.168.100.44 1deleteWhen 9876 brokerClusterName = DefaultClusterbrokerName = broker-bbrokerId = 1deleteWhen = 48brokerRole = SLAVEflushDiskType = ASYNC_FLUSHlistenPort = 11011storePathRootDir = / app/rocketmq/store-b

Broker-master.properties file on the 192.168.100.44 machine:

NamesrvAddr = 192.168.100.43 04fileReservedTime 9876 Taiwan 192.168.100.44 0deleteWhen 9876 brokerClusterName = DefaultClusterbrokerName = broker-bbrokerId = 0deleteWhen = 48brokerRole = SYNC_MASTERflushDiskType = ASYNC_FLUSHlistenPort = 10911storePathRootDir = / app/rocketmq/store-b

Broker-slave.properties file on the 192.168.100.44 machine:

NamesrvAddr = 192.168.100.43 04fileReservedTime 9876 Taiwan 192.168.100.44 1deleteWhen 9876 brokerClusterName = DefaultClusterbrokerName = broker-abrokerId = 1deleteWhen = 48brokerRole = SLAVEflushDiskType = ASYNC_FLUSHlistenPort = 11011storePathRootDir = / app/rocketmq/store-a

Then start the master node and slave node of the two servers using the following command

Nohup sh bin/mqbroker-c conf/broker-master.properties &

Nohup sh bin/mqbroker-c conf/broker-slave.properties &

Such a highly available RockerMQ cluster is set up. We log in to the visual operation and maintenance management interface to check the cluster status, and the cluster starts normally.

Important parameter description

This section mainly describes the parameters used in the configuration file of Broker

NamesrvAddr = 192.168.100.43RV 9876 Ten 192.168.100.44RU 9876

Specify the address of the NameServer, which can be multiple.

BrokerClusterName = DefaultCluster

Cluster addresses can be divided into multiple Cluster if there are a large number of clusters, and each Cluster is used by a business group.

BrokerName = broker-a

The name of Broker, Master and Slave indicate the relationship by using the same Broker name to indicate which Master's Slave a Slave is.

BrokerId = 1

A Master can have multiple Slave,0 to represent Master, and an ID greater than 0 represents a different Slave.

FileReservedTime = 48

The length of time, in hours, for which messages are saved on disk, and messages that time out are automatically deleted.

DeleteWhen = 04

Corresponding to the fileReservedTime parameter, indicates when to delete the message. The default is 4: 00 in the morning.

BrokerRole = SYNC_MASTER

There are three optional parameters for brokerRole: SYNC_MASTER,ASYNC_MASTER,SLAVE. SYNC and ASYNC represent the mechanism for synchronizing messages between MASTER and SLAVE. SYNC means that the message synchronization between Slave and Master is completed before returning to the status of successful delivery.

FlushDiskType = ASYNC_FLUSH

FlushDiskType refers to disk flushing strategy. Available values are ASYNC_FLUSH and SYNC_FLUSH, which represent synchronous and asynchronous flushing respectively. In the synchronous case, the message returns to the successful state only if it is actually written to disk; in the asynchronous case, the successful status is returned after the message is written to the page_cache.

ListenPort = 11011

The port on which Broker listens. A server starts multiple Broker. You need to set different listening ports to avoid port conflicts.

StorePathRootDir = / app/rocketmq/store-a

The root directory where messages and configuration information are stored.

Visual management platform

RocketMQ can use rocketmq-externals as the OPS management platform with the address https://github.com/apache/rocketmq-externals of Github. We need to download the source code and then compile it manually. The process is as follows:

download

Download the source code of the RocketMQ visual management tool rocketmq-externals from github (https://github.com/apache/rocketmq-externals)

Packing

After the download is completed, change to the rocketmq-console directory and use the maven command to package mvn clean package-Dmaven.test.skip=true

Generate the executable file rocketmq-console-ng-1.0.1.jar after the packaging is completed

Running

Start using the java-jar rocketmq-console-ng-1.0.1.jar-- server.port=8080-- rocketmq.config.namesrvAddr=xxxx.xxx.xxx.xxx:9876 command

Note here that two parameters need to be set:

-- server.port is the port on which the web application is running. If it is not set, the default is 8080.

-- rocketmq.config.namesrvAddr is the address of the RocketMQ naming service. If NameServer is a cluster, use English; Segmentation

Visit

The browser accesses xxx.xxx.xxx.xxx:8080 to enter the console interface, and the effect is as follows

SpringBoot integrates RocketMQ

Integrating RocketMQ in SpringBoot mainly uses rocketmq-spring-boot-starter components. Here is the detailed integration process.

Introduce the component rocketmq-spring-boot-starter depending on org.apache.rocketmq rocketmq-spring-boot-starter 2.1.0 to modify the application.yml and add the RocketMQ related configuration rocketmq: name-server: 192.168.100.43 RocketMQ 9876 producer: group: test-group send-message-timeout: 3000

If it is a cluster, multiple name-server are used in English; split.

Write message producer MessageProduce/** * Description: * rocketMQ message sending method * @ author javadaily * / @ Componentpublic class MessageProduce {@ Autowired private RocketMQTemplate rocketMQTemplate; / * send message * @ param topic topic * @ param message message body * / public void sendMessage (String topic,String message) {this.rocketMQTemplate.convertAndSend (topic,message);}}

Use RocketMQTemplate to send messages

Write message consumer MessageConsumer@Slf4j@Component@RocketMQMessageListener (topic = "test-topic", consumerGroup = "test-group", selectorExpression = "*") public class MessageConsumer implements RocketMQListener {@ Override public void onMessage (String message) {log.info ("received message is {}", message);}}

Consumers only need to inherit the RocketMQListener class, focusing on the @ RocketMQMessageListener annotation on the implementation class, and the configuration of topic and consumerGroup needs to be consistent with that of the message producer.

Write a unit test to send the message @ RunWith (SpringRunner.class) @ SpringBootTestpublic class MessageProduceTest {@ Autowired private MessageProduce messageProduce; @ Testpublic void testSendMessage () {messageProduce.sendMessage ("test-topic", "Hello, Java Daily Log");}} Test

Start the springboot application first, and then execute the test case.

At this point, I believe you have a deeper understanding of "what is the method of micro-service architecture design RocketMQ foundation and environment integration". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.