CN113760572A - Message processing method and device - Google Patents

Abstract

The invention discloses a message processing method and device, and relates to the technical field of computers. A specific implementation of the method includes: obtaining a first item attribute change message; according to the item identifier, judging whether there is a second item attribute change message corresponding to the item identifier in the message cache data; if not, according to the the first item attribute change message, create a second item attribute change message corresponding to the item identifier in the message cache data, and push the first item attribute change message to the message queue; The first item attribute change message updates the second item attribute change message, and increases the number of message changes corresponding to the second item attribute change message, so as to determine whether to change the second item attribute according to the number of message changes. Messages are pushed to the message queue. This embodiment reduces the frequency of sending change messages within a short period of time.

Description

A message processing method and device

technical field

The present invention relates to the field of computer technology, and in particular, to a message processing method and device.

Background technique

With the development of e-commerce business and the expansion and enrichment of item application scenarios, item attributes are growing rapidly, corresponding to the formation of thousands of attributes or attribute groups, such as basic attributes including name, price, and inventory, including Sales attributes and specifications of colors, sizes, etc. Based on this, in order to adapt to the rapid growth of item attributes to better support business search and display, many business systems use message queues to transmit item attribute change messages to improve user experience.

In the process of implementing the present invention, the inventor found that there are at least the following problems in the prior art: every change message of item attributes will be pushed to the message queue. The message queue will be frequently used to transmit messages, which will occupy a large amount of server resources and bandwidth; for downstream message consumers, the corresponding item attributes need to be updated frequently and under high load according to the change message, and there may be a large number of them. Invalid update results in wasting resources and reducing processing efficiency.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present invention provide a message processing method and device, which can ensure the immediacy of the message, and avoid a short time by merging one or more received item attribute change messages in the message cache data. Change messages are frequently sent within the system, thereby avoiding downstream message consumers from frequently updating item attributes in a short period of time, and reducing the waste of resources such as servers.

To achieve the above purpose, according to an aspect of the embodiments of the present invention, a message processing method is provided, including:

acquiring a first item attribute change message, where the first item attribute change message indicates an item identifier and one or more updated item attribute values corresponding to the item identifier;

According to the item identifier, determine whether there is a second item attribute change message corresponding to the item identifier in the message cache data:

If it does not exist, create a second item attribute change message corresponding to the item identifier in the message cache data according to the first item attribute change message, and push the first item attribute change message to the message queue ;

If it exists, update the second item attribute change message according to the first item attribute change message, and increase the number of message changes corresponding to the second item attribute change message, so as to determine whether to change the information according to the number of message changes. The second item attribute change message is pushed to the message queue.

Optionally, also include:

In the case where a second item attribute change message corresponding to the item identifier is created in the message cache data, a first timing task is started for the second item attribute change message, so that after the first threshold time elapses, according to the The number of changes of the message is used to determine whether to push the second item attribute change message to the message queue.

Optionally, the judging whether to push the second item attribute change message to the message queue according to the number of changes of the message includes:

Determine whether the current message change times corresponding to the second item attribute change message is greater than the corresponding message change times when the second item attribute change message was created:

If it is greater than that, push the second item attribute change message to the message queue, and delete the second item attribute change message from the message cache data;

If it is not greater than the value, the second item attribute change message is directly deleted from the message cache data.

Optionally, also include:

starting a second timing task for the message cache data to periodically traverse the second item attribute change messages in the message cache data;

And when the sending time corresponding to the second item attribute change message is less than the current time, it is judged whether to push the second item attribute change message to the message queue according to the number of message changes, and the sending time indicates is the sum of the creation time of the second item attribute change message and the second threshold time.

Optionally, the first item attribute change message is acquired by parsing a database log file, and the database is used to store the item identifier and the corresponding item attribute value.

Optionally, also include:

In the case of pushing the second item attribute change message to the message queue, notify the consumer of the second item attribute change message to obtain the corresponding item identifier from the database by means of a remote procedure call The changed item attribute value of .

Optionally, also include:

A cache period is set for the second item attribute change message, so that after the cache period elapses, the second item attribute change message is deleted from the message cache data.

Optionally, also include:

Before determining whether there is a second item attribute change message corresponding to the item identifier in the message cache data according to the item identifier, determine whether the message type corresponding to the first item attribute change message can be used to create a corresponding second item Property change message.

Optionally, also include:

Before determining whether there is a second item attribute change message corresponding to the item identifier in the message cache data according to the item identifier, it is determined whether a second item attribute change message can be created within the current time period.

Optionally, the second item attribute change message is stored in the message cache data in the form of a key-value pair.

In order to achieve the above object, according to another aspect of the embodiments of the present invention, a message processing device is provided, including: an item attribute change message acquisition module and an item attribute change message processing module; wherein,

The item attribute change message acquisition module is configured to acquire a first item attribute change message, where the first item attribute change message indicates an item identifier and one or more updated item attribute values corresponding to the item identifier;

The item attribute change message processing module is configured to determine, according to the item identifier, whether there is a second item attribute change message corresponding to the item identifier in the message cache data:

If it does not exist, create a second item attribute change message corresponding to the item identifier in the message cache data according to the first item attribute change message, and push the first item attribute change message to the message queue ;

If it exists, update the second item attribute change message according to the first item attribute change message, and increase the number of message changes corresponding to the second item attribute change message, so as to determine whether to change the information according to the number of message changes. The second item attribute change message is pushed to the message queue.

Optionally, it also includes: a timing task starting module; wherein,

The timing task starting module is configured to start a first timing task for the second item attribute change message in the case of creating a second item attribute change message corresponding to the item identifier in the message cache data, to After the first threshold time has elapsed, whether to push the second item attribute change message to the message queue is determined according to the number of times of message change.

Optionally, the judging whether to push the second item attribute change message to the message queue according to the number of changes of the message includes:

Determine whether the current message change times corresponding to the second item attribute change message is greater than the message change times corresponding to the creation of the second item attribute change times:

If it is greater than that, push the second item attribute change message to the message queue, and delete the second item attribute change message from the message cache data;

If it is not greater than the value, the second item attribute change message is directly deleted from the message cache data.

Optionally, the timing task startup module is also used to:

starting a second timing task for the message cache data to periodically traverse the second item attribute change messages in the message cache data;

And in the case that the sending time corresponding to the second item attribute change message is less than the current time, determine whether to push the second item attribute change message to the message queue according to the number of changes of the message; wherein, the sending The time indicates the sum of the creation time of the second item attribute change message and the second threshold time.

Optionally, the item attribute change message acquisition module is configured to acquire the first item attribute change message by parsing a database log file, and the database is used to store the item identifier and the corresponding item attribute value.

Optionally, the item attribute change message processing module is further configured to:

In the case of pushing the second item attribute change message to the message queue, notify the consumer of the second item attribute change message to obtain the corresponding item identifier from the database by means of a remote procedure call The changed item attribute value of .

Optionally, the item attribute change message processing module is further configured to:

A cache period is set for the second item attribute change message, so that after the cache period elapses, the second item attribute change message is deleted from the message cache data.

Optionally, the item attribute change message processing module is further configured to:

Before determining whether there is a second item attribute change message corresponding to the item identifier in the message cache data according to the item identifier, determine whether the message type corresponding to the first item attribute change message can be used to create a corresponding second item Property change message.

Optionally, the item attribute change message processing module is further configured to:

Before determining whether there is a second item attribute change message corresponding to the item identifier in the message cache data according to the item identifier, it is determined whether a second item attribute change message can be created within the current time period.

Optionally, the second item attribute change message is stored in the message cache data in the form of a key-value pair.

To achieve the above object, according to yet another aspect of the embodiments of the present invention, an electronic device for message processing is provided, comprising: one or more processors; a storage device for storing one or more programs,

When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above message processing methods.

In order to achieve the above object, according to another aspect of the embodiments of the present invention, a computer-readable medium is provided, on which a computer program is stored, and when the program is executed by a processor, any one of the above message processing methods is implemented. the method described.

An embodiment of the above invention has the following advantages or beneficial effects: by creating or continuously updating the second item attribute change message in the message cache data when the first item attribute change message is received, the obtained item attribute change message is realized. The combination of one or more first item attribute change messages avoids frequent sending of change messages in a short period of time, thereby preventing downstream message consumers from frequently updating item attributes in a short period of time, reducing the occupation of servers and bandwidth, and reducing It eliminates the waste of resources caused by frequent and invalid updating of item attributes. At the same time, by directly sending the first item attribute change message through the message queue when creating the second item attribute change message, the immediacy of the downstream message consumer receiving the item attribute change message is ensured.

Further effects of the above non-conventional alternatives will be described below in conjunction with specific embodiments.

Description of drawings

The accompanying drawings are used for better understanding of the present invention and do not constitute an improper limitation of the present invention. in:

1 is a schematic diagram of a main flow of a message processing method according to an embodiment of the present invention;

2 is a schematic diagram of a main flow of another message processing method according to an embodiment of the present invention;

3 is a schematic diagram of a main flow of a further message processing method according to an embodiment of the present invention;

4 is a schematic diagram of main modules of a message processing apparatus according to an embodiment of the present invention;

5 is an exemplary system architecture diagram to which an embodiment of the present invention may be applied;

FIG. 6 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, which include various details of the embodiments of the present invention to facilitate understanding and should be considered as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted from the following description for clarity and conciseness.

FIG. 1 is a schematic diagram of a main flow of a message processing method according to an embodiment of the present invention. As shown in FIG. 1 , the message processing method may specifically include the following steps:

Step S101: Obtain a first item attribute change message, where the first item attribute change message indicates an item identifier and one or more item attribute values corresponding to the item identifier.

Among them, the item identifier refers to information that can be used to distinguish different items, such as the product SKU code. Item attributes refer to any attribute information actually used to describe an item or related to an item, including but not limited to item name, item price, item inventory, item color, item size, specification parameters, whether it is self-operated, POP, item pictures, Item videos, item reviews, and more. Take the mobile phone with the item ID 0001 as an example. With the promotion and sales activities, the value of the mobile phone's actual selling price, actual inventory and other attribute information are constantly changing, especially for Double Eleven and Double Ten. During the second-class classic promotion, the value of its attribute information will change frequently in a short period of time. Accordingly, in order to ensure the reliability of the displayed or recorded item attribute information, it is necessary to continuously update the item attribute value according to the actual situation.

Generally speaking, the item management system can use the database to record the attribute information corresponding to different items, and can continuously update the item attribute value corresponding to the item identifier recorded in the database by adding, deleting and changing data according to the actual situation, so as to meet the downstream needs. Consumers who obtain item attribute information continuously send item attribute change messages.

Based on this, the first item attribute change message can be acquired by parsing a database log file, and the database is used to store the item identifier and the corresponding item attribute value. It can be understood that, this embodiment only uses a database to store attribute information corresponding to an item for description, and in the actual implementation process, a distributed cache or other storage methods may be used for replacement. Specifically, taking the MySQL database as an example for illustration, the incremental log of the MySQL database, that is, the Binlog log file, can be parsed through canal, so as to obtain the property change message of the first item. More specifically, the first item attribute change message indicates the item ID (eg, 0001), and one or more item attribute values after the modification corresponding to the item ID, such as the color is yellow; the price is 100; the stock is 23, etc.

Step S102, according to the item identifier, determine whether there is a second item attribute change message corresponding to the item identifier in the message cache data. Specifically, if it does not exist, continue to execute the following step S103; if it exists, continue to execute the following step S104.

That is to say, after the first item attribute change message is obtained by parsing the database log file, the first item attribute change message is not directly sent to the downstream message consumer through the message queue, but is first merged in the message cache data for One or more first item attribute change messages identified by the same item, that is, creating or continuously updating second item attribute change messages according to the first item attribute change messages. In this way, the problem of occupying a large amount of server resources and bandwidth due to frequent changes of item attributes in a short period of time and frequent sending of change messages to the downstream is avoided.

The second item attribute change message indicates one or more newly updated item attribute values corresponding to the item identifier. Specifically, the second item attribute change message may only indicate the latest updated one or more item attribute values indicated by the first item attribute change message, or may indicate the latest updated item according to the first item attribute change message Identifies all corresponding item attribute values. For example, all the item attributes corresponding to the item identifier 0001 only include color, size, price, and inventory as an example for illustration. The updated second item attribute change message may only indicate that the price corresponding to the item ID 0001 is 100 and the stock is 23, or it may indicate that the price corresponding to the item ID 0001 is 100, the stock is 23, and the color is yellow , the size is 5.5 inches, etc.

Furthermore, the second item attribute change message may be stored in the form of a key-value pair in the stored message cache data, that is, a Hash data structure is used to store the second item attribute change message. For example, taking the storage of message cache data in Redis as an example, the second item identifier can be used as the key value, and the corresponding updated attribute value of one or more items is stored as the value value. In this way, the item identifier can be queried by querying the item identifier. This key value method can quickly determine whether the value corresponding to the item identifier already exists in Redis, that is, the second item attribute change message. In addition, in the actual execution process, information such as the sending time of the item identifier, the number of times of message changes, and the like can also be correspondingly stored in the value value.

The sending time is determined by the sum of the creation time of the second item attribute change message and the second threshold time, and the second threshold time indicates the use of message cache data to merge one or more first item attribute messages corresponding to the same item identifier The length of time can be preset according to the actual situation, such as 30s, 50s, etc. The number of message changes indicates the number of times the attribute information corresponding to the item identifier is changed within the second threshold time since the creation of the second item attribute change message, that is, the total number of received first item attribute change messages. By default, the corresponding message change times when the second item attribute change message is created is 1. It can be understood that the number of times of message change corresponding to the creation of the second item attribute change message can also be set to a value other than 1 according to the actual situation.

In an optional embodiment, the method further includes: before judging whether there is a second item attribute change message corresponding to the item ID in the message cache data according to the item ID, judging whether a first item attribute change message can be created within the current time period 2. Item attribute change message.

That is to say, in the actual execution process, it can be reasonably set to use the message cache data to merge the first item attribute change message, that is, create the second item attribute change message, according to the time rule of frequent change of item attributes in a short period of time. time period. For example, during the Double Eleven, Double Twelve and other big promotions, the strategy of creating a second item attribute change message is adopted, and this strategy is not adopted at other times. In this way, it can not only reduce the frequent sending of the first item attribute change message directly to the downstream in a short period of time, causing the downstream message consumers to update the item attribute value frequently and ineffectively, but also take into account the immediacy of sending the item attribute change message to the downstream, Ensure that the attributes of items received by downstream consumers are worthy of high availability.

Further, it also includes: before judging whether there is a second item attribute change message corresponding to the item ID in the message cache data according to the item ID, judging whether the message type corresponding to the first item attribute change message is available. to create a corresponding second item attribute change message.

That is to say, in addition to determining whether to adopt the strategy of creating a second item attribute change message in the current time period according to the time rule of frequent changes in item attributes in a short period of time, it can also be more fine-grained according to downstream message consumers The immediacy requirements of item attribute change messages, that is, different message types, determine whether to use message cache data to merge the first item attribute change message, that is, create a second item attribute change message to reduce the frequency of sending change messages in a short period of time. For example, during the Double Eleven and Double Twelve promotions, there is a high requirement for the immediacy of item attribute change messages such as price and inventory, so instead of creating a second item attribute change message, all the obtained items can be sent directly. The obtained first item attribute change message containing price and inventory, to ensure the immediacy and high availability of downstream acquisition price and inventory; on the other hand, for the first item attribute change that only indicates item attributes such as item pictures and item videos The immediacy requirements of messages are relatively low. In order to reduce the occupation of server resources or bandwidth, you can consider creating a second item attribute change message to reduce the frequency of sending change messages in a short period of time.

Step S103, according to the first item attribute change message, create a second item attribute change message corresponding to the item identifier in the message cache data, and push the first item attribute change message to a message queue.

That is to say, in the case where there is no second item attribute change message corresponding to the item identifier in the message cache data, a second item attribute change message is created to obtain one or more items corresponding to the item identifier later. In the case of the first item attribute change message, update the second item attribute change message instead of directly sending the subsequently acquired first item attribute change message, so as to reduce the frequency of sending item attribute change messages corresponding to the same item identifier in a short period of time . At the same time, when the second item attribute change message is created according to the first item attribute change message, the first item attribute change message is directly pushed to the message queue, so that downstream message consumers can update the corresponding item according to the first item attribute change message Attribute value, to a certain extent, ensures the immediacy and high availability of item attribute change messages.

More specifically, this embodiment is only described by taking the second item attribute change message indicating the latest updated item attribute value or values corresponding to the item identifier as an example. If the first item attribute change message indicates the item identifier 0001 The corresponding price is 100 and the stock is 23, then the second item attribute change message created according to the first item attribute change message also indicates that the price corresponding to the item identifier 0001 is 100 and the stock is 23. It can be understood that the second item attribute change message can also indicate other item attribute values corresponding to the item identifier 0001, as well as the corresponding message change times (such as ₁ ), sending time T1, etc., wherein the sending time _T1 indicates The sum of the current time T ₀ and the second threshold time (such as 30s), that is, in the next 30s, if the first item attribute change message corresponding to the item ID 0001 is obtained, it will not be sent directly but will be updated accordingly. Item attribute change message; until the corresponding sending time has passed after 30s, the second item attribute change message can be directly pushed to the message queue, and the second item attribute change message can be deleted from the message cache data to avoid the same Repeated sending of the second item attribute change message reduces resource waste.

Further, it also includes: in the case of creating a second item attribute change message corresponding to the item identifier in the message cache data, starting a first timing task for the second item attribute change message, so as to After a threshold time, it is determined whether to push the second item attribute change message to the message queue according to the number of times of message change. That is to say, in order to ensure the immediacy of sending the second item attribute change message in the message cache data, a timer task can be set through the Timer, so that after the first threshold time (such as 40s), the second item in the message cache data is sent. The second item attribute change message is pushed to the message queue, and the second item attribute change message is deleted from the message cache data, so as to avoid repeated transmission of the same second item attribute change message and reduce resource waste.

More specifically, judging that the message queue sends the second item attribute change message according to the message change times includes: judging whether the current message change times corresponding to the second item attribute change message is greater than creating the first item attribute change message. The number of times of message change corresponding to the second item attribute change message: if it is greater than that, push the second item attribute change message to the message queue, and delete the second item attribute change message from the message cache data; If it is not greater than the value, the second item attribute change message is directly deleted from the message cache data.

Step S104: Update the second item attribute change message according to the first item attribute change message, and increase the number of message changes corresponding to the second item attribute change message, so as to determine whether to change the message according to the number of message changes. The second item attribute change message is pushed to the message queue.

Specifically, this embodiment is only described by taking the second item attribute change message indicating the latest updated item attribute value or values corresponding to the item identifier as an example. If the first item attribute change message indicates that the item identifier 0001 corresponds to The price is 100, the inventory is 23, and the second item attribute change message in the message cache data indicates that the price is 150, the inventory is 50, and the corresponding message change times is 3, then update according to the first item attribute change message The following second item attribute change message indicates that the price corresponding to the item ID 0001 is 100, the inventory is 23, and the corresponding message change times is increased to 5, that is, since the creation of the second item attribute change message, a total of 5 such items have been obtained successively. The first item attribute change message corresponding to the item identifier.

Furthermore, in order to avoid the failure of the Timer, causing the set first timing task to fail to be executed normally, and thus making the second item attribute change message fail to be sent normally, a periodic second timing is also set by means of a daemon process. The task, for example, is executed every 10s to ensure the immediacy and high availability of the downstream message consumer receiving the second item attribute change message. Specifically, it also includes: starting a second timing task for the message cache data to periodically traverse the second item attribute change messages in the message cache data; and sending the second item attribute change message corresponding to the message cache data. When the time is less than the current time, it is judged whether to push the second item attribute change message to the message queue according to the number of message changes, and the sending time indicates the difference between the creation time of the second item attribute change message and the Sum of the second threshold time.

More specifically, in the process of periodically facilitating message cache data, if it is found that the sending time corresponding to the second item attribute change message is less than the current time, that is, the second item attribute change message should be sent but not sent, then further judge the Whether the current message change times corresponding to the second item attribute change message is greater than the corresponding message change times when the second item attribute change message was created (eg 1): if it is greater, it means that the second item attribute change message has been changed since it was created If the change occurs, the second item attribute change message is pushed to the message queue, and the second item attribute change message is deleted from the message cache data to avoid repeated sending; The second item attribute change message has not changed since it was created, so the second item attribute change message is directly deleted from the message cache data to avoid repeated transmission.

In addition, in order to avoid residual accumulation of expired second item attribute change messages in the message cache data due to Timer failure or daemon process failure, etc., to ensure the effective utilization of the storage space of the message cache device, it also includes: for the first item A cache period is set for the second item attribute change message, so that after the cache period elapses, the second item attribute change message is deleted from the message cache data. For example, taking the cache period, that is, TTL (Time To Live) as 100s, as an example, the second item attribute change message that has been stored for 100s in the message cache data is automatically cleared.

It is worth noting that, in the case where the second item attribute change message only indicates the latest updated one or more item attribute values indicated by the first item attribute change message, if the successively acquired first item attribute change messages indicate If the updated item attributes are different, only the latest updated second item attribute change message will be pushed to the message queue, and there is a situation where the updated item attributes are omitted, which reduces the second item attributes received downstream to a certain extent. Change message high availability. However, if the second item attribute change message indicates all the item attribute values corresponding to the latest updated item identifier according to the first item attribute change message, although the omission of the updated item attribute can be avoided, with the rapid increase of the item attribute, the limitation is limited. Due to the size of the message capacity, the number of updated item attributes indicated in the second item attribute change message is limited.

Based on this, while avoiding frequent sending of change messages to the downstream in a short period of time, ensuring the high availability of the second item attribute change message received downstream, the method further includes: pushing the second item attribute change message to the message queue In the case of notifying the consumer of the second item attribute change message, the changed item attribute value corresponding to the item identifier is obtained from the database by means of a remote procedure call. That is to say, by creating a second item attribute change message, the frequency of sending item attribute change messages to the downstream is reduced, so that the downstream message consumers can know the item attribute change and use the RPC remote procedure call from the storage. Query the latest updated attribute values of all items corresponding to the item ID in the MySQL database of the attribute information corresponding to the item ID.

Based on the above embodiment, when the first item attribute change message is received, the second item attribute change message is created or continuously updated in the message cache data, so as to realize the change of one or more acquired first item attributes. The merging of messages avoids frequent sending of change messages in a short period of time, thereby preventing downstream message consumers from frequently updating item attributes in a short period of time, reducing the occupation of servers and bandwidth, and reducing the frequent and invalid update of item attributes. Waste of resources. At the same time, by directly sending the first item attribute change message through the message queue when creating the second item attribute change message, the immediacy of the downstream message consumer receiving the item attribute change message is ensured.

Referring to FIG. 2 , on the basis of the foregoing embodiment, the embodiment of the present invention provides another message processing method, which may specifically include the following steps:

Step S201: Obtain a first item attribute change message, where the first item attribute change message indicates an item identifier and one or more updated item attribute values corresponding to the item identifier.

Step S202, determining whether a second item attribute change message can be created within the current time period. If it can be created, continue to execute the following step S203; if it cannot be created, continue to execute the following step S204.

Step S203, on the basis that the second item attribute change message can be created in the current time period, determine whether the message type corresponding to the first item attribute change message can be used to create the corresponding second item attribute change message. If it can be created, continue to execute the following step S205; if it cannot be created, continue to execute the following step S204.

Step S204, on the basis that the second item attribute change message cannot be created, push the first item attribute change message to the message queue.

Step S205, according to the item identifier, determine whether there is a second item attribute change message corresponding to the item identifier in the message cache data. If it exists, continue to execute the following step S207; if not, continue to execute the following step S206.

Step S206, according to the first item attribute change message, create a second item attribute change message corresponding to the item identifier in the message cache data, and push the first item attribute change message to a message queue. This embodiment is described only when the number of message changes corresponding to the second item attribute change message is 1 at this time.

Step S207: Update the second item attribute change message according to the first item attribute change message, and increase the number of message changes corresponding to the second item attribute change message.

Step S208, starting a first timed task for the second item attribute change message. In this way, after a first threshold time (eg 30s) has elapsed, it may be determined whether to push the second item attribute change message to the message queue according to the number of times of message change.

Step S209, after the first threshold time has elapsed, determine whether the current message change times corresponding to the second item attribute change message is greater than 1, that is, determine whether the second item attribute change message has been updated since it was created. If it is greater than, continue to execute the following step S210; if not, continue to execute the following step S211.

Step S210, push the second item attribute change message to the message queue, and delete the second item attribute change message deleted from the message cache data.

Step S211, directly delete the second item attribute change message from the message cache data. It can be understood that, since the corresponding first item attribute change message has been sent when the second item attribute change message is created, if the second item attribute change message has not been updated, in order to avoid repeated transmission, you can directly Delete the second item attribute change message, while saving cache space.

On this basis, in order to avoid the failure of the Timer, the set first timed task cannot be executed normally, and thus the second item attribute change message cannot be sent normally, and a periodic second timer is also set by means of a daemon process. Timed tasks, such as executing once every 10s, ensure the immediacy and high availability of downstream message consumers receiving the second item attribute change message. The specific message processing method involved is shown in Figure 3, and the corresponding steps are as follows:

Step S301 , start a second timing task for the message cache data, so as to periodically traverse the second item attribute change messages in the message cache data.

Step S302, judging whether the sending time corresponding to the second item attribute change message is less than the current time; wherein, the sending time indicates the sum of the creation time of the second item attribute change message and a second threshold time (eg 30s). If it is less than that, it means that the second item attribute change message should be sent but not sent, and the following step S303 is continued; The operation of the second item attribute change message continues to traverse other second item attribute change messages.

Step S303, judging whether the current message change times corresponding to the second item attribute change message is greater than the corresponding message change times (ie, 1) when the second item attribute change message was created. If it is greater than that, it means that the second item attribute change message has changed since it was created, and the following step S304 is continued; Step S305.

Step S304, push the second item attribute change message to the message queue, and delete the second item attribute change message from the message cache data to avoid repeated sending.

Step S305, directly delete the second item attribute change message from the message cache data to avoid repeated sending.

Referring to FIG. 4 , on the basis of the above-mentioned embodiments, an embodiment of the present invention provides a message processing apparatus 400, including: an item attribute change message acquisition module 401 and an item attribute change message processing module 402; wherein,

The item attribute change message obtaining module 401 is configured to obtain a first item attribute change message, where the first item attribute change message indicates an item identifier and one or more updated item attribute values corresponding to the item identifier;

The item attribute change message processing module 402 is configured to determine, according to the item identifier, whether there is a second item attribute change message corresponding to the item identifier in the message cache data:

If it does not exist, create a second item attribute change message corresponding to the item identifier in the message cache data according to the first item attribute change message, and push the first item attribute change message to the message queue ;

If it exists, update the second item attribute change message according to the first item attribute change message, and increase the number of message changes corresponding to the second item attribute change message, so as to determine whether to change the information according to the number of message changes. The second item attribute change message is pushed to the message queue.

In an optional implementation manner, it further includes: a timing task starting module 403; wherein,

The timing task starting module is configured to start a first timing task for the second item attribute change message in the case of creating a second item attribute change message corresponding to the item identifier in the message cache data, to After the first threshold time has elapsed, whether to push the second item attribute change message to the message queue is determined according to the number of times of message change.

In an optional implementation manner, the judging whether to push the second item attribute change message to the message queue according to the number of changes of the message includes:

Determine whether the current message change times corresponding to the second item attribute change message is greater than the message change times corresponding to the creation of the second item attribute change times:

If it is greater than that, push the second item attribute change message to the message queue, and delete the second item attribute change message from the message cache data;

If it is not greater than the value, the second item attribute change message is directly deleted from the message cache data.

In an optional implementation manner, the timing task starting module 403 is further configured to:

starting a second timing task for the message cache data to periodically traverse the second item attribute change messages in the message cache data;

And in the case that the sending time corresponding to the second item attribute change message is less than the current time, determine whether to push the second item attribute change message to the message queue according to the number of changes of the message; wherein, the sending The time indicates the sum of the creation time of the second item attribute change message and the second threshold time.

In an optional implementation manner, the item attribute change message obtaining module 401 is configured to obtain the first item attribute change message by parsing a database log file, and the database is used to store the item identifier and the The corresponding item attribute value.

In an optional implementation manner, the item attribute change message processing module 402 is further configured to:

In the case of pushing the second item attribute change message to the message queue, notify the consumer of the second item attribute change message to obtain the corresponding item identifier from the database by means of a remote procedure call The changed item attribute value of .

In an optional implementation manner, the item attribute change message processing module 402 is further configured to:

A cache period is set for the second item attribute change message, so that after the cache period elapses, the second item attribute change message is deleted from the message cache data.

In an optional implementation manner, the item attribute change message processing module 402 is further configured to:

Before determining whether there is a second item attribute change message corresponding to the item identifier in the message cache data according to the item identifier, determine whether the message type corresponding to the first item attribute change message can be used to create a corresponding second item Property change message.

In an optional implementation manner, the item attribute change message processing module 402 is further configured to:

Before determining whether there is a second item attribute change message corresponding to the item identifier in the message cache data according to the item identifier, it is determined whether a second item attribute change message can be created within the current time period.

In an optional implementation manner, the second item attribute change message is stored in the message cache data in the form of a key-value pair. Specifically, the available message data caching device includes, but is not limited to, Redis and the like.

FIG. 5 shows an exemplary system architecture 500 to which a message processing method or a message processing apparatus according to an embodiment of the present invention may be applied.

As shown in FIG. 5 , the system architecture 500 may include terminal devices 501 , 502 , and 503 , a network 504 and a server 505 . The network 504 is a medium used to provide a communication link between the terminal devices 501 , 502 , 503 and the server 505 . Network 504 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the terminal devices 501, 502, 503 to interact with the server 505 through the network 504 to receive or send messages and the like. Client applications may be installed on the terminal devices 501 , 502 and 503 .

The terminal devices 501, 502, 503 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

The server 505 may be a server that provides various services, for example, a server that manages the attributes of items browsed by users using the terminal devices 501 , 502 , and 503 . The background management server may analyze and process the received item attribute change message, etc., and feed back the second item attribute change message as a result of the processing to the terminal device.

It should be noted that the message processing method provided in the embodiment of the present invention is generally executed by the server 505 , and accordingly, the message processing apparatus is generally set in the server 505 .

It should be understood that the numbers of terminal devices, networks and servers in FIG. 5 are only illustrative. There can be any number of terminal devices, networks and servers according to implementation needs.

Referring to FIG. 6 below, it shows a schematic structural diagram of a computer system 600 suitable for implementing a terminal device according to an embodiment of the present invention. The terminal device shown in FIG. 6 is only an example, and should not impose any limitations on the functions and scope of use of the embodiments of the present invention.

As shown in FIG. 6, a computer system 600 includes a central processing unit (CPU) 601, which can be loaded into a random access memory (RAM) 603 according to a program stored in a read only memory (ROM) 602 or a program from a storage section 608 Instead, various appropriate actions and processes are performed. In the RAM 603, various programs and data necessary for the operation of the system 600 are also stored. The CPU 601 , the ROM 602 , and the RAM 603 are connected to each other through a bus 604 . An input/output (I/O) interface 605 is also connected to bus 604 .

The following components are connected to the I/O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc. ; and a communication section 609 including a network interface card such as a LAN card, a modem, and the like. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I/O interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 610 as needed so that a computer program read therefrom is installed into the storage section 608 as needed.

In particular, the processes described above with reference to the flowcharts may be implemented as computer software programs in accordance with the disclosed embodiments of the present invention. For example, embodiments disclosed herein include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 609 and/or installed from the removable medium 611 . When the computer program is executed by the central processing unit (CPU) 601, the above-described functions defined in the system of the present invention are performed.

It should be noted that the computer-readable medium shown in the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or a combination of any of the above. More specific examples of computer readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read only memory (EPROM or flash memory), fiber optics, portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, however, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code therein. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device . Program code embodied on a computer readable medium may be transmitted using any suitable medium including, but not limited to, wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

The modules involved in the embodiments of the present invention may be implemented in a software manner, and may also be implemented in a hardware manner. The described unit (or "module") can also be set in the processor, for example, it can be described as: a processor includes an item attribute change message acquisition module and an item attribute change message processing module. Wherein, the names of these modules do not constitute a limitation on the unit itself under certain circumstances. For example, the timing task starting module may also be described as a "timing task starting module module".

As another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or may exist alone without being assembled into the device. The above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by a device, the device includes: acquiring a first item attribute change message, the first item attribute change message indicating The item ID and one or more updated item attribute values corresponding to the item ID; according to the item ID, determine whether there is a second item attribute change message corresponding to the item ID in the message cache data: if not, Then, according to the first item attribute change message, create a second item attribute change message corresponding to the item identifier in the message cache data, and push the first item attribute change message to the message queue; if it exists, Then update the second item attribute change message according to the first item attribute change message, and increase the number of message changes corresponding to the second item attribute change message, so as to determine whether to change the second item according to the number of message changes. The item attribute change message is pushed to the message queue.

According to the technical solution of the embodiment of the present invention, when the first item attribute change message is received, the second item attribute change message is created or continuously updated in the message cache data, so that the obtained one or more items The merging of item attribute change messages avoids frequent sending of change messages in a short period of time, thereby preventing downstream message consumers from frequently updating item attributes in a short period of time, reducing the occupation of servers and bandwidth, and reducing frequent invalid updates. Waste of resources caused by item attributes. At the same time, by directly sending the first item attribute change message through the message queue when creating the second item attribute change message, the immediacy of the downstream message consumer receiving the item attribute change message is ensured.

The above-mentioned specific embodiments do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (13)

1. A message processing method, comprising:

acquiring a first article attribute change message, wherein the first article attribute change message indicates an article identifier and one or more updated article attribute values corresponding to the article identifier;

according to the item identifier, judging whether a second item attribute change message corresponding to the item identifier exists in message cache data:

if the first item attribute change message does not exist, creating a second item attribute change message corresponding to the item identifier in the message cache data according to the first item attribute change message, and pushing the first item attribute change message to a message queue;

if the attribute change message exists, updating the second item attribute change message according to the first item attribute change message, and increasing the message change times corresponding to the second item attribute change message so as to judge whether to push the second item attribute change message to the message queue according to the message change times.

2. The message processing method according to claim 1, further comprising:

and under the condition that a second item attribute change message corresponding to the item identifier is created in the message cache data, starting a first timing task aiming at the second item attribute change message, and judging whether to push the second item attribute change message to the message queue according to the message change times after a first threshold time.

3. The message processing method according to claim 2, wherein the determining whether to push the second item attribute change message to the message queue according to the message change times includes:

judging whether the current message change times corresponding to the second article attribute change message is larger than the message change times corresponding to the second article attribute change message:

if so, pushing the second item attribute change message to the message queue, and deleting the second item attribute change message from the message cache data;

and if not, directly deleting the second item attribute change message from the message cache data.

4. The message processing method according to claim 3, further comprising:

starting a second timing task for the message cache data to periodically traverse a second item attribute change message in the message cache data;

and judging whether to push the second item attribute change message to the message queue according to the message change times under the condition that the sending time corresponding to the second item attribute change message is less than the current time, wherein the sending time indicates the sum of the creation time of the second item attribute change message and a second threshold time.

5. The message processing method according to claim 3 or 4,

and acquiring the first article attribute change message by analyzing a database log file, wherein the database is used for storing the article identification and the corresponding article attribute value.

6. The message processing method according to claim 5, further comprising:

and under the condition that the second article attribute change message is pushed to the message queue, informing a consumer of the second article attribute change message to acquire the changed article attribute value corresponding to the article identifier from the database in a remote process call mode.

7. The message processing method according to claim 3, further comprising:

and setting a cache term for the second item attribute change message, so that the second item attribute change message is deleted from the message cache data after the cache term passes.

8. The message processing method according to claim 1, further comprising:

before judging whether a second item attribute change message corresponding to the item identifier exists in the message cache data according to the item identifier, judging whether the message type corresponding to the first item attribute change message can be used for creating the corresponding second item attribute change message.

9. The message processing method according to claim 1, further comprising:

and judging whether a second item attribute change message can be created in the current time period before judging whether the second item attribute change message corresponding to the item identifier exists in the message cache data according to the item identifier.

10. The message processing method of claim 1,

and storing the second item attribute change message in the message cache data in a key value pair mode.

11. A message processing apparatus, comprising: the system comprises an article attribute change message acquisition module and an article attribute change message processing module; wherein,

the article attribute change message acquiring module is configured to acquire a first article attribute change message, where the first article attribute change message indicates an article identifier and one or more updated article attribute values corresponding to the article identifier;

the article attribute change message processing module is configured to determine, according to the article identifier, whether a second article attribute change message corresponding to the article identifier exists in the message cache data:

if the first item attribute change message does not exist, creating a second item attribute change message corresponding to the item identifier in the message cache data according to the first item attribute change message, and pushing the first item attribute change message to a message queue;

if the attribute change message exists, updating the second item attribute change message according to the first item attribute change message, and increasing the message change times corresponding to the second item attribute change message so as to judge whether to push the second item attribute change message to the message queue according to the message change times.

12. An electronic device for message processing, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-10.

13. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-10.

Images