Method and system for message processing

Abstract

Processing a message includes receiving at a message processing system the message that is distributed by a message distributor, the message having a message type, based at least in part on the message type, locating among a plurality of subscriber groups a subscriber group that subscribes to the message type, each of the plurality of subscriber groups having a unique identifier and comprising one or more message subscriber nodes, at least some of the one or more message subscriber nodes in each of the plurality of subscriber groups being connected to the message processing system, and transmitting the message to a message subscriber node that belongs to the subscriber group that is located.

What is claimed is: 
     
         1 . (canceled) 
     
     
         2 . A system, comprising:
 a message distributor to send a message to a middleware server, the message having a message type, wherein the middleware server is connected to a first plurality of message subscriber nodes associated with a first subscriber group and to a second plurality of message subscriber nodes associated with a second subscriber group, wherein a message subscriber node of the first plurality of message subscriber nodes associated with the first subscriber group is configured to perform a first processing function and a message subscriber node of the second plurality of message subscriber nodes associated with the second subscriber group is configured to perform a second processing function, wherein the first processing function is different from the second processing function;   the middleware server to:
 receive the message from the message distributor; 
 determine that the first subscriber group subscribes to the message type; and 
 transmit the message to a selected message subscriber node that belongs to the first subscriber group, wherein the selected message subscriber node is configured to process the message based at least in part on the first processing function associated with the first subscriber group; and 
   a memory coupled to the processor and configured to provide the processor with instructions.   
     
     
         3 . The system of  claim 2 , wherein the selected message subscriber node is randomly selected among the first plurality of message subscriber nodes associated with the first subscriber group. 
     
     
         4 . The system of  claim 2 , wherein the selected message subscriber node is selected to correspond to an idle message subscriber node in the first plurality of message subscriber nodes associated with the first subscriber group. 
     
     
         5 . The system of  claim 2 , wherein the middleware server is connected to the first plurality of message subscriber nodes associated with the first subscriber group and the second plurality of message subscriber nodes associated with the second subscriber group in a long connection mode. 
     
     
         6 . The system of  claim 5 , wherein the middleware server is further to connect to a newly added message subscriber node in the first subscriber group, the newly added message subscriber node being associated with the first subscriber group based on a unique identifier of the first subscriber group. 
     
     
         7 . The system of  claim 2 , wherein the system further includes a database to store a corresponding relationship of the message type and a unique identifier of the first subscriber group based at least in part on subscription information from a message subscriber. 
     
     
         8 . The system of  claim 2 , wherein in the event that a message subscriber node in the first plurality of message subscriber nodes fails, message subscriber nodes other than the failed message subscriber node in the first plurality of message subscriber nodes are to continue processing received messages. 
     
     
         9 . The system of  claim 2 , wherein a number of message subscriber nodes included in the first plurality of message subscriber nodes is configured to be dynamically adjusted based on message traffic volume. 
     
     
         10 . A method, comprising:
 sending a message to a middleware server, the message having a message type, wherein the middleware server is connected to a first plurality of message subscriber nodes associated with a first subscriber group and to a second plurality of message subscriber nodes associated with a second subscriber group, wherein a message subscriber node of the first plurality of message subscriber nodes associated with the first subscriber group is configured to perform a first processing function and a message subscriber node of the second plurality of message subscriber nodes associated with the second subscriber group is configured to perform a second processing function, wherein the first processing function is different from the second processing function;   receiving the message from the message distributor;   determining that the first subscriber group subscribes to the message type; and   transmitting the message to a selected message subscriber node that belongs to the first subscriber group, wherein the selected message subscriber node is configured to process the message based at least in part on the first processing function associated with the first subscriber group.   
     
     
         11 . The method of  claim 10 , wherein the selected message subscriber node is randomly selected among the first plurality of message subscriber nodes associated with the first subscriber group. 
     
     
         12 . The method of  claim 10 , wherein the selected message subscriber node is selected to correspond to an idle message subscriber node in the first plurality of message subscriber nodes associated with the first subscriber group. 
     
     
         13 . The method of  claim 10 , wherein the middleware server is connected to the first plurality of message subscriber nodes associated with the first subscriber group and to the second plurality of message subscriber nodes associated with the second subscriber group in a long connection mode. 
     
     
         14 . The method of  claim 13 , wherein the middleware server is further connected to a newly added message subscriber node in the first subscriber group, the newly added message subscriber node being associated with the first subscriber group based on a unique identifier of the first subscriber group. 
     
     
         15 . The method of  claim 10  further comprising storing a corresponding relationship of the message type and a unique identifier of the first subscriber group based at least in part on subscription information from a message subscriber. 
     
     
         16 . The method of  claim 10 , wherein in the event that a message subscriber node in the first plurality of message subscriber nodes fails, message subscriber nodes other than the failed message subscriber node in the first plurality of message subscriber nodes are configured to continue processing received messages. 
     
     
         17 . The method of  claim 10 , wherein a number of message subscriber nodes included in the first plurality of message subscriber nodes is configured to be dynamically adjusted based on message traffic volume. 
     
     
         18 . A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising instructions for:
 sending a message to a middleware server, the message having a message type, wherein the middleware server is connected to a first plurality of message subscriber nodes associated with a first subscriber group and to a second plurality of message subscriber nodes associated with a second subscriber group, wherein a message subscriber node of the first plurality of message subscriber nodes associated with the first subscriber group is configured to perform a first processing function and a message subscriber node of the second plurality of message subscriber nodes associated with the second subscriber group is configured to perform a second processing function, wherein the first processing function is different from the second processing function;   receiving the message from the message distributor;   determining that the first subscriber group subscribes to the message type; and   transmitting the message to a selected message subscriber node that belongs to the first subscriber group, wherein the selected message subscriber node is configured to process the message based at least in part on the first processing function associated with the first subscriber group.