Message isolation forwarding method and system

Abstract

The invention relates to a routing method which comprises the following steps: S1, receiving, identifying and storing message data: uniformly receiving the message data, calling a processor to perform attribute identification on the received message data, recording an identification result, and classifying and storing the message data according to the identified message type; S2, carrying out differentiated processing and forwarding of the message data: carrying out differentiated processing on the message data according to the message type of the message data, carrying out conversion processing on the message data by a corresponding service processor according to the message type to obtain service processing data, and uniformly delivering the service processing data to an associated application dubbo of a corresponding parameter key; S3, returning a notification result and judging whether the notification result is abnormal or not: returning the notification result to the routing processor, judging whether the analyzed notification result is normal or not, if the message is normally processed and responded, consuming and submitting the queue message by the program, if the message is subjected to exception processing response, unifying exception interception records to an exception data management table, and triggering an exception processor to automatically compensate and retry.

Description

technical field [0001] The present invention relates to the technical field of routing methods, in particular to a message isolation and forwarding method and system. Background technique [0002] With the rapid development of business, there are more and more business types of messages, and the messages in the distributed system need to be forwarded to different business processing channels for different logical processing. Each additional message type needs to be judged by adding conditions. The sending logic has not been scaled horizontally. At the same time, manual configuration notification addresses are added to notify the target system through http requests. Automate retries. [0003] At present, the message notification can only be forwarded through the local configuration specified forwarding address, the program is hard-coded to match the message prefix, and the http request notification is transferred to the target system; each system has not uniformly implemente...

AI Technical Summary

Problems solved by technology

Each additional message type needs to be judged by adding conditions. The sending logic has not been scaled horizontally. At the same time, manual configuration notification addresses are added to notify the target system through http requests. Automated retries

[0003] At present, the message notification can only be forwarded through the local configuration specified forwarding address, the program is hard-coded to match the message prefix, and the http request notification is transferred to the target system; each system has not uniformly implemented exception automatic processing, and the message loss cannot be collected to the unified service for automatic reset Sending compensation, relying on manual processing by post-management

[0004] The initial planning of the intermediate forwarding system is limited to the transmission of messages by two single services, and can only support http requests; with the rapid development of business, there are more and more types of message services, and the interaction logic of each system to process messages becomes more and more complex

[0005] The storage structure of abnormal messages that appear in their respective business processes is not uniform, there is no policy management for storing abnormal messages, and no policy clearing action is taken after retransmission is completed, resulting in data accumulation, which in turn leads to heavy data query pressure; The http method needs to maintain and manage the address of each retry; there is no unified exception retry management mechanism, which leads to duplication of exception retry codes in various channels

[0006] As a result, the rigid agreement between the systems is not conducive to subsequent program expansion and maintenance, the request mode is single, and the reliability of the message cannot be guaranteed. The intermediate system is prone to network and service exceptions without a compensation retry mechanism; the configuration operation is cumbersome and easy to miss; rely on configuration Address notification, network changes increase system maintenance work; manual configuration to notify each application address, configuration is cumbersome, inconvenient to operate, and easy to miss; automatic retry in the application, code redundancy, and does not support unified automatic exception retry, Bad for code management

Images