CN112667681A

CN112667681A - Data caching method and device and storage medium

Info

Publication number: CN112667681A
Application number: CN202011521246.5A
Authority: CN
Inventors: 陈雷
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2020-12-21
Filing date: 2020-12-21
Publication date: 2021-04-16

Abstract

The method comprises the steps of obtaining a target user behavior event, for example, obtaining some operations triggered by a user, further writing the target user behavior event into a preset message queue, obtaining user data corresponding to the target user behavior event in the preset message queue through at least one service interface, and caching the user data, namely actively caching the user data used by other subsequent operations in advance. Thus, for some activities, such as a double eleven shopping activity and a new mobile phone shopping activity, the data of the user to participate can be actively cached in the embodiment of the application. In the first moment of the robbery, the user interacts with the cache to complete the order, and the order cannot directly interact with the database, so that frequent access of the user to the database is reduced, and the stability of the server is improved.

Description

Data caching method and device and storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a data caching method, an apparatus, and a storage medium.

Background

Currently, e-commerce is rapidly developing, and merchants communicate product or service information to specific users through e-commerce websites provided by third parties over the internet. The user places an order through the Internet, pays in a certain payment mode, and the merchant delivers the product through the logistics enterprise to finally complete the product transaction. When a user purchases at an e-commerce website, the commonly adopted process is as follows: the user clicks a product detail page on a shopping interface provided by a certain shopping Application program (APP) of the mobile phone to check product detail information, the user is interested and clicks to place an order, a new user needs to fill user data, an old user generally uses a server to automatically fill the user data, and then the user submits an order and completes work such as payment.

In the related art, for an old user, when the server first pulls the user data of the user, the server queries the user data in the cache, and if the cache does not exist, the server queries the user data from the database. If the user data is queried in the database, the server will typically place the queried user data in a cache. Therefore, when the user places an order again, the server can directly acquire the user data from the cache, so that the user experience is improved, the service performance is also improved, and the pressure of a database on the server is reduced.

However, for some activities, such as the double eleven shopping activity and the new mobile phone shopping activity, a large number of users may access the activities in the first moment of shopping, and problems may occur if the user data is cached in the above manner. For example, the above caching is performed only after the user first triggers, and thus, if a large number of users access the server for the first time at the same time, the server may be unstable.

Disclosure of Invention

In order to solve the problems in the prior art, the present application provides a data caching method, apparatus and storage medium.

In a first aspect, an embodiment of the present application provides a data caching method, where the method includes:

acquiring a target user behavior event;

writing the target user behavior event into a preset message queue;

acquiring user data corresponding to the target user behavior event in the preset message queue through at least one service interface;

and caching the user data.

In a possible implementation manner, the obtaining the target user behavior event includes:

acquiring a live broadcast service access interface calling request;

and generating the target user behavior event according to the calling request.

In a possible implementation manner, the generating the target user behavior event according to the invocation request includes:

acquiring the stay time of a user after the user enters the live broadcast service according to the calling request, wherein the user enters the live broadcast service through a live broadcast service entry interface;

and if the stay time is greater than a first preset time threshold, generating the target user behavior event.

determining whether to acquire the call request for the first time;

and if the calling request is acquired for the first time, generating the target user behavior event according to the calling request.

In a possible implementation manner, the invocation request carries an identifier of the live broadcast service;

after the writing of the target user behavior event into a preset message queue, the method further includes:

acquiring service parameters of the live broadcast service according to the identification of the live broadcast service;

determining whether a shopping cart parameter exists in the service parameters;

and if the shopping cart parameters exist in the service parameters, executing the step of acquiring the user data corresponding to the target user behavior events in the preset message queue through at least one service interface.

In a possible implementation manner, the invocation request further carries an identifier of a user, the at least one service interface includes a user address service interface, and the user data includes a user address;

the obtaining, through at least one service interface, user data corresponding to the target user behavior event in the preset message queue includes:

and acquiring the user address corresponding to the user identification through the user address service interface.

In one possible implementation, the at least one service interface further includes a user product service interface, and the user data further includes an order list;

the obtaining, through at least one service interface, user data corresponding to the target user behavior event in the preset message queue further includes:

and acquiring an order list corresponding to the user identification through the user product service interface.

In a possible implementation manner, after the caching the user data, the method further includes:

and creating and completing the order of the user according to the user address corresponding to the cached user identification.

acquiring a stay event of a user on a product detail interface;

and generating the target user behavior event according to the stay event.

In one possible implementation manner, the stay event carries a stay time of the user on the product detail interface, and the stay time is greater than a second preset time threshold.

In a possible implementation manner, the generating the target user behavior event according to the stay event includes:

determining whether to acquire the stay event for the first time;

and if the stopping event is acquired for the first time, generating the target user behavior event according to the stopping event.

acquiring a sliding event of a user on a product detail interface;

and generating the target user behavior event according to the sliding event.

In one possible implementation manner, the sliding event carries a sliding proportion of the user on the product detail interface, and the sliding proportion is greater than a preset proportion threshold.

In a possible implementation manner, the generating the target user behavior event according to the sliding event includes:

determining whether to acquire the sliding event for the first time;

and if the sliding event is acquired for the first time, generating the target user behavior event according to the sliding event.

In one possible implementation, the at least one service interface includes a user address service interface, and the user data includes a user address;

acquiring the identification of the user;

In one possible implementation, the at least one service interface further includes a user product service interface, and the user data further includes an order list.

In a second aspect, an embodiment of the present application provides a data caching apparatus, where the apparatus is applied to a process of placing an order by a user, and the apparatus includes:

the event obtaining module is used for obtaining a target user behavior event;

the event writing module is used for writing the target user behavior event into a preset message queue;

the data acquisition module is used for acquiring user data corresponding to the target user behavior event in the preset message queue through at least one service interface;

and the data caching module is used for caching the user data.

In a possible implementation manner, the event obtaining module is specifically configured to:

acquiring a live broadcast service access interface calling request;

and generating the target user behavior event according to the calling request.

determining whether to acquire the call request for the first time;

In a possible implementation manner, the invocation request carries an identifier of the live service.

The data acquisition module is further configured to acquire a service parameter of the live broadcast service according to the identifier of the live broadcast service after the event writing module writes the target user behavior event into a preset message queue;

determining whether a shopping cart parameter exists in the service parameters;

In a possible implementation manner, the invocation request further carries an identifier of a user, the at least one service interface includes a user address service interface, and the user data includes a user address.

The data acquisition module is specifically configured to:

In a possible implementation manner, after caching the user data, the data caching module is further configured to:

acquiring a stay event of a user on a product detail interface;

and generating the target user behavior event according to the stay event.

determining whether to acquire the stay event for the first time;

acquiring a sliding event of a user on a product detail interface;

and generating the target user behavior event according to the sliding event.

determining whether to acquire the sliding event for the first time;

In one possible implementation, the at least one service interface includes a user address service interface, and the user data includes a user address.

The data acquisition module is specifically configured to:

acquiring the identification of the user;

The data acquisition module is specifically configured to:

In a third aspect, an embodiment of the present application provides a data caching apparatus, including:

a processor;

a memory; and

a computer program;

wherein the computer program is stored in the memory and configured to be executed by the processor, the computer program comprising instructions for performing the method of the first aspect.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a computer program is stored, and the computer program causes a server to execute the method according to the first aspect.

In a fifth aspect, the present application provides a computer program product, which includes computer instructions for executing the method of the first aspect by a processor.

According to the data caching method, the data caching device and the storage medium, the target user behavior event is obtained, for example, certain operations triggered by a user are obtained, then the target user behavior event is written into a preset message queue, user data corresponding to the target user behavior event in the preset message queue is obtained through at least one service interface, and the user data is cached, namely, the user data used by other post-positioned operations are actively cached in advance. Thus, for some activities, such as a double eleven shopping activity and a new mobile phone shopping activity, the data of the user to participate can be actively cached in the embodiment of the application. In the first moment of the robbery, the user interacts with the cache to complete the order, and the order cannot directly interact with the database, so that frequent access of the user to the database is reduced, and the stability of the server is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.

Fig. 1 is a schematic flowchart illustrating a process of placing an order by a user according to an embodiment of the present application;

fig. 2 is a schematic diagram of a data caching system according to an embodiment of the present application;

FIG. 3 is a schematic diagram of another data caching system according to an embodiment of the present application;

fig. 4 is a schematic flowchart of a data caching method according to an embodiment of the present application;

fig. 5 is a schematic diagram illustrating a server processing a user behavior event in a preset message queue according to an embodiment of the present application;

fig. 6 is a schematic flowchart of another data caching method according to an embodiment of the present application;

fig. 7 is a schematic flowchart of another data caching method according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a data caching apparatus according to an embodiment of the present application;

fig. 9 is a schematic diagram of a basic hardware architecture of a data caching device provided in the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms "first," "second," "third," and "fourth," if any, in the description and claims of this application and the above-described figures are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The existing users place orders through the internet, pay in a certain payment mode, and the merchants distribute products through logistics enterprises to finally complete product transactions. When a user purchases at an e-commerce website, the commonly adopted process is as follows: a user clicks a product detail page on a shopping interface provided by a certain shopping APP of a mobile phone to check product detail information, is interested and then clicks to place an order, a new user needs to fill in user data, an old user generally uses a server to automatically fill in the user data, and then the user submits an order to complete work such as payment.

For example, the process of placing an order by a user is generally illustrated in FIG. 1. When a user purchases a product through the e-commerce website, the order can be placed to the server through the terminal device. For example, a user installs a certain shopping APP on a mobile phone, and clicks to enter a product detail page on a shopping interface provided by the APP, so as to check product detail information, be interested in and then click to place an order. After receiving the order information from the user, the server will typically automatically populate the user information for the old user. The server needs to pull the user data, when the user data is pulled for the first time, the user data is inquired in the cache, and if the cache does not exist, the user data is inquired from the database. If the user data is queried in the database, the server will typically place the queried user data in a cache. And finally, the server automatically fills the user information according to the cached user data, completes the order of the user and feeds the order back to the terminal equipment. The user can check the order information through the terminal equipment and submit the order to the server through the terminal equipment after checking that the order is correct. And after checking the order submitted by the user, the server feeds back payment information to the terminal equipment. And the user completes payment through the terminal equipment based on the payment information. After detecting the payment completion information of the user, the server can feed back the payment success information of the terminal equipment, can prestore an order processing flow and feed back the processing state of the current order.

However, for some activities, such as the double eleven shopping activity and the new mobile phone shopping activity, a large number of users may access the activities in the first moment of shopping, and problems may occur if the user data is cached in the above manner. For example, the above caching is performed only after the user first triggers, and thus, if a large number of users access the server for the first time at the same time, the server may be unstable. That is, in the prior art, only after the user completes the first access, for example, after the order is placed for the first time, if the user accesses again, the server will pull the user data and place the user data in the cache. Thus, for the first-time accessed users, if the number of the users is large, a large number of users need to directly interact with the database, so that the response speed of the server is slow, and the server may be unstable.

Therefore, an embodiment of the present application provides a data caching method, which is applied to order placing processing by a user, and obtains a target user behavior event, for example, certain operations triggered by the user, and further obtains user data corresponding to the target user behavior event, and caches the user data, that is, actively caches user data used by other operations placed at a later time in advance. Thus, for some activities, such as a double eleven shopping activity and a new mobile phone shopping activity, the data of the user to participate can be actively cached in the embodiment of the application. In the first moment of the robbery, the user interacts with the cache to complete the order, and the order cannot directly interact with the database, so that frequent access of the user to the database is reduced, the response speed of the server is increased, and the stability of the server is improved.

In the embodiment of the present application, the target user behavior event may be determined according to an actual situation, for example, determined by the server according to information sent by the client. Illustratively, taking the example that a user enters a live broadcast service, a terminal device of the user, for example, a mobile phone of the user, installs an APP. The APP includes a native page or an inline H5 page. The user triggers certain operations in the page and sends the operations to the server to interact with the server.

Optionally, as shown in fig. 2, fig. 2 is a schematic diagram of a data caching system architecture provided in the embodiment of the present application. In fig. 2, the user enters the live service as an example. The architecture includes a client 21 and a server 22.

In the specific implementation process, the user triggers certain operations in a page of a certain APP installed in the client 21 and sends the operations to the server. For example, to enter a live service, the user calls a live service entry interface to the server 22, i.e., sends a live service entry interface call request to the server 22. The server 22 generates a target user behavior event according to the request, and obtains the user data corresponding to the target user behavior event, so as to cache the user data, that is, actively cache the user data used by other operations in the future. Therefore, if a plurality of users watch the live broadcast service online, the embodiment of the application can actively cache the data of the users. After the products are introduced by the live broadcast service anchor, the user can interact with the cache when limited-time robbery is carried out on the products, the ordering and the robbery of the products are finished, the direct interaction with the database is avoided, frequent access of the user to the database is reduced, and the stability of the server is improved.

In addition, the target user behavior event may also be one or more events sent by the client to the server. Illustratively, taking an example that a user enters shopping at a certain shopping APP, a terminal device of the user, such as a mobile phone of the user, installs the certain shopping APP. The APP may also include a native page or an inline H5 page. The user triggers certain operations when accessing the operation-related page, and sends the operations to the server to interact with the server.

Optionally, as shown in fig. 3, fig. 3 is a schematic diagram of another data caching system architecture provided in the embodiment of the present application. In fig. 3, the user enters the live service as an example. The architecture includes a client 31 and a server 32.

In the specific implementation process, the user triggers certain operations in a page of a certain shopping APP installed by the client terminal 31 and sends the operations to the server. Such as a user stopping or sliding on a product detail interface, etc. The client 31 may send the user a stop event or slide event, etc. at the above-described product detail interface to the server 32. The server 32 generates a target user behavior event according to the stay event or the slide event, and acquires user data corresponding to the target user behavior event, thereby caching the user data, that is, actively caching user data used for other operations in the future. Therefore, if a plurality of users are in a process of purchasing a certain product, the data of the users to participate can be actively cached in the embodiment of the application. In the first moment of the robbery, the user interacts with the cache to finish the ordering and the robbery of the product, but does not directly interact with the database, so that the pressure of the server for reading the database concurrently is reduced, and the stability of the server is improved.

It is to be understood that the illustrated structure of the embodiments of the present application does not constitute a specific limitation to the data cache architecture. In other possible embodiments of the present application, the architecture may include more or less components than those shown in fig. 2 and fig. 3, or combine some components, or split some components, or arrange different components, which may be determined according to an actual application scenario and is not limited herein. The components shown in fig. 2 and 3 may be implemented in hardware, software, or a combination of software and hardware.

The technical solutions of the present application are described below with several embodiments as examples, and the same or similar concepts or processes may not be described in detail in some embodiments.

Fig. 4 is a flowchart illustrating a data caching method according to an embodiment of the present application, where the data caching method according to the embodiment of the present application may be applied to a process of placing an order by a user, and the method may be executed by any device that executes the data caching method, and the device may be implemented by software and/or hardware. As shown in fig. 4, based on the system architecture shown in fig. 2 or fig. 3, the data caching method provided in the embodiment of the present application includes the following steps:

s401: and acquiring a target user behavior event.

In the embodiment of the present application, the execution subject is taken as the server in fig. 2 or fig. 3 as an example. The obtaining of the target user behavior event may be a target user behavior event generated according to a call request after the server obtains a live broadcast service access interface call request, for example, after the live broadcast service access interface call request sent by the client is obtained. Or the server may obtain a staying event of the user on the product detail interface, for example, obtain a staying event of the user on the product detail interface sent by the client, and generate a target user behavior event according to the staying event. The server may also obtain a sliding event of the user on the interface at the product detail interface, for example, obtain a sliding event of the user on the interface at the product detail interface sent by the client, and generate a target user behavior event according to the sliding event.

Here, the server may further obtain the stay event and the slide event, and further generate a target user behavior event and the like according to the stay event and the slide event, which may be determined specifically according to an actual situation, and this is not particularly limited in this embodiment of the present application.

In addition, after acquiring the live broadcast service access interface call request, the server can determine whether to exchange the call request for the first time. If the server acquires the call request for the first time, the target user behavior event can be generated according to the call request. Similarly, after acquiring the stay event of the user on the product detail interface or the slide event of the user on the interface, the server may also determine whether to acquire the stay event for the first time, and determine whether to acquire the slide event for the first time. If the server acquires the stay event for the first time, the target user behavior event can be generated according to the stay event. If the server acquires the sliding event for the first time, the target user behavior event can be generated according to the sliding event.

S402: and writing the target user behavior event into a preset message queue.

Before writing the target user behavior event into a preset message queue, the server may set the preset message queue in a cache, or set the preset message queue in a preset file, which may be determined according to actual conditions.

Here, the server may not be able to process the user behavior events in real time, for example, a large number of user behavior events are generated at the moment of a robbery, and the server may not be able to process a large number of concurrent user behavior events in real time. In order to solve the problem, in the embodiment of the application, the server sets the preset message queue, and after the user behavior event is obtained, the obtained user behavior event is written into the preset message queue, so that the user behavior event in the preset message queue can be processed according to an actual situation, for example, the user behavior event in the preset message queue is processed according to the frequency of processing once every ten minutes, and therefore, the problem that the server cannot process the user behavior event in real time when a large number of user behavior events are concurrent is solved.

S403: and acquiring user data corresponding to the target user behavior event in the preset message queue through at least one service interface.

When the server processes the user behavior event in the preset message queue, the server may obtain the user data corresponding to the target user behavior event in the queue through at least one service interface according to an asynchronous task processing principle, for example, based on a group of consumer components, as shown in fig. 5.

Here, the at least one service interface may include a user address service interface, and the user data may include a user address. The server may obtain, through the user address service interface, a user address corresponding to the target user behavior event in the preset message queue. For example, the server may obtain, from a database, a user address corresponding to the target user behavior event in the preset message queue through the user address service interface.

In addition, the at least one service interface may further include a user product service interface, and the user data may further include an order list, such as a user order. The server may obtain, through the user product service interface, an order list corresponding to the target user behavior event in the preset message queue. For example, the server may obtain, from a database through the user product service interface, an order list corresponding to the target user behavior event in the preset message queue.

S404: and caching the user data.

Here, after caching the user data, the server may create an order for completing the user according to the cached user data. The server can actively cache the data of the user without the need of triggering the user for the first time, so that the data can be directly acquired from the cache when the user places an order, concurrent access of a large number of users to the server database is avoided, and the performance of the server is improved. Moreover, the server does not need to add an additional popularization flow, and the cost is reduced.

According to the embodiment of the application, the server acquires the target user behavior event, for example, acquires some operations triggered by the user, and then writes the target user behavior event into the preset message queue, so that the user data corresponding to the target user behavior event in the preset message queue is acquired through at least one service interface, and the user data is cached, that is, the server actively caches the user data used by other subsequent operations in advance. In this way, for some activities, such as a double eleven shopping activity, a new handset preemption activity, the server may actively cache data for users to participate. In the first moment of the robbery, the user interacts with the cache to complete the order, and the order cannot directly interact with the database, so that frequent access of the user to the database is reduced, the response speed of the server is improved, and the stability of the server is improved.

Here, the obtained target user behavior event may be a target user behavior event generated according to a call request after the server obtains a live broadcast service entry interface call request. The calling request carries an identifier of live broadcast service, and the server can obtain service parameters of the live broadcast service according to the identifier of the live broadcast service after writing the target user behavior event into a preset message queue, so as to judge whether a shopping cart exists in the live broadcast service and further determine whether to execute subsequent steps. Fig. 6 is a flowchart illustrating another data caching method according to an embodiment of the present application. As shown in fig. 6, the method includes:

s601: and acquiring a live broadcast service access interface calling request.

S602: and generating a target user behavior event according to the calling request, wherein the calling request carries the identification of the live broadcast service.

Here, the user calls the entry interface before entering the live service, and the client may send a live service entry interface call request to the server. And the server generates the target user behavior event according to the calling request, further acquires user data corresponding to the target user behavior event, and caches the user data. Assuming that 10 users enter the live service, the server actively caches data of 10 ten thousand users. Like this, after the product is introduced in the anchor, the product of putting on the shelf carries out the limited time and robs for purchase, if 1w user clicks the purchase simultaneously, because user address data has all been cached, the flow experience of placing an order is improved. Moreover, at the moment of the first-time shopping, the user interacts with the cache, so that frequent access of the user to the database is reduced, and the stability of the server is improved.

When the server generates the target user behavior event according to the call request, the server may first feed back the live broadcast service entry interface to the client according to the call request, and then obtain the dwell time of the user after entering the live broadcast service through the live broadcast service entry interface. And if the time is greater than a first preset time threshold, the server generates the target user behavior event. The first preset time threshold may be set according to actual conditions, for example, 10 seconds.

In the embodiment of the application, after the user enters the live broadcast service, the server obtains the stay time of the user in the live broadcast service, and if the stay time reaches a certain threshold, for example, the first preset time threshold, it indicates that the probability that the user subsequently participates in the live broadcast service is higher, for example, the probability of a rush-purchase activity when participating in a product limit released by the live broadcast service is higher. And the server correspondingly generates the target user behavior event, so that the user data corresponding to the target user behavior event is obtained and cached. Therefore, when the user performs limited-time rush purchase on the product, the user can interact with the cache, and the stability of the server is improved.

In addition, the server can determine whether to acquire the calling request for the first time when generating the target user behavior event according to the calling request. For example, the invocation request carries an identifier of a user, and the server may determine whether to obtain the invocation request for the first time according to the identifier of the user and the obtained user identifier in the invocation request of the live broadcast service access interface. If the calling request is obtained for the first time, the server can generate the target user behavior event according to the calling request.

Here, after the server first obtains the call request, the server generates the target user behavior event according to the call request, further obtains user data corresponding to the target user behavior event, and caches the user data. Therefore, when the user places an order again, the server can directly acquire the corresponding user data from the cache, the pressure of the database on the server is reduced, and the user experience is also improved.

S603: and writing the target user behavior event into a preset message queue.

Step S603 is the same as the implementation of step S402, and is not described herein again.

S604: and acquiring the service parameters of the live broadcast service according to the identification of the live broadcast service.

Here, the identification of the live service may include an Identity Document (ID) of the live service. The server may pre-store a corresponding relationship between an identifier (for example, the ID) of the live broadcast service and a service parameter of the live broadcast service, where the service parameter may be understood as a parameter related to the live broadcast service, and may include a shopping cart parameter, a product parameter, and the like.

The server can obtain the service parameters of the live broadcast service according to the identification of the live broadcast service carried by the calling request and the corresponding relation.

S605: and determining whether the service parameters comprise shopping cart parameters.

S606: and if the shopping cart parameters exist in the service parameters, acquiring user data corresponding to the target user behavior events in the preset message queue through at least one service interface.

If the service parameters comprise the shopping cart parameters, the live broadcast service is the shopping live broadcast service. After the product is introduced by the anchor, the live broadcast service provides time-limited rush-purchase activity for the product. Therefore, the server needs to actively cache the data of the user, so that the user can interact with the cache when the user performs limited-time rush purchase on the product, and frequent access of the user to the database is reduced.

The invocation request may also carry an identifier of the user, such as a user identification (uid) of the user. The at least one service interface may comprise a user address service interface and the user data may comprise a user address. When the server obtains the user data corresponding to the target user behavior event in the preset message queue through at least one service interface, the server can obtain the user address corresponding to the user identifier through the user address service interface. For example, the server may obtain, from a database, a user address corresponding to the identifier of the user through the user address service interface. The corresponding relation between the user identification and the user address can be prestored in the database. In this way, the server may obtain, through the user address service interface, the user address corresponding to the user identifier from the correspondence stored in the database. Here, the user may enter the live service through a terminal-installed APP, such as a cell phone-installed APP. The user identifier and the user address may be filled in by the user when the user registers information with the APP. The database stores the user identification and user address filled by the user.

And the server acquires a user address corresponding to the user identifier, caches the user address, and completes the order of the user according to the cached user address.

In addition, the at least one service interface may further include a user product service interface, and the user data may further include an order list. When the server obtains the user data corresponding to the target user behavior event in the preset message queue through at least one service interface, the server can obtain an order list corresponding to the user identifier through the user product service interface. For example, the server may obtain the order list corresponding to the identifier of the user from a database through the user product service interface. The corresponding relation between the user identification and the order list can be prestored in the database. In this way, the server may obtain the order list corresponding to the user identifier from the corresponding relationship stored in the database through the user product service interface. Here, the order list may be information of products that the user has completed purchasing, which is recorded in the database.

S607: and caching the user data.

After the target user behavior event is written into the preset message queue, the server can acquire the service parameters of the live broadcast service according to the identification of the live broadcast service, so that whether a shopping cart exists in the live broadcast service is judged, whether follow-up steps are executed is determined, and accordingly, normal follow-up processing is guaranteed. For example, when there is a shopping cart in the live broadcast service, the subsequent steps are executed. Wherein, the live broadcast service is provided with a shopping cart to show that the live broadcast service is a shopping live broadcast service. After the product is introduced by the anchor, the live broadcast service provides time-limited rush-purchase activity for the product. Therefore, the server needs to actively cache the data of the user, so that the user can interact with the cache to complete an order when the user performs limited-time rush purchase on a product, frequent access of the user to the database is reduced, and the stability of the server is improved.

In addition, the obtained target user behavior event may also be one or more events sent by the client to the server. The event sent by the client to the server may be a stay event or a slide event. The stay event can be understood as a stay event of a user at a product detail interface of a certain shopping APP. The sliding event can be understood as a sliding event of the user on the product detail interface of the shopping APP. And the server generates a target user behavior event according to the stay event or the slide event and the like, acquires user data corresponding to the target user behavior event, and caches the user data. Fig. 7 is a flowchart illustrating another data caching method according to an embodiment of the present application. As shown in fig. 7, the method includes:

s701: and acquiring a stay event of the user on the product detail interface.

S702: and generating a target user behavior event according to the stay event.

The stay event may carry a stay time of the user on the product detail interface, where the stay time is greater than a second preset time threshold. The second preset time threshold may be set according to actual conditions, for example, 10 seconds. Illustratively, when a user browses the product detail interface, the interface times to determine whether the user stays for a certain time, that is, whether the staying time of the user is greater than a second preset time threshold. And if the stay time of the user is greater than a second preset time threshold, the client sends the stay event to the server. And the server generates a target user behavior event according to the stay event.

Here, the client sends the stay event to the server only when the stay time of the user is greater than a certain value, so that the accuracy of subsequent processing can be further improved. Because the stay time of the user is more than a certain value, the probability that the user needs to purchase the product subsequently is higher, for example, the user participates in the time-limited shopping activity of the product. And the server correspondingly generates the target user behavior event, so that the user data corresponding to the target user behavior event is obtained and cached. Therefore, when the user performs limited-time rush purchase on the product, the user can interact with the cache, and the stability of the server is improved.

In this embodiment, when the server generates the target user behavior event according to the stay event, it may determine whether to acquire the stay event for the first time. For example, the stay event carries an identifier of a user, and the server may determine whether to acquire the stay event for the first time according to the identifier of the user and the acquired user identifier of the user in the stay event of the product detail interface. If the stay event is obtained for the first time, the server can generate the target user behavior event according to the stay event, further obtain user data corresponding to the target user behavior event, and cache the user data. Therefore, when the user places an order again, the server can directly acquire corresponding user data from the cache, the pressure of the database on the server is reduced, and the user experience is improved.

In addition, the server can also acquire the residence time of the user on the product detail interface, which is periodically sent by the client, so that the total residence time of the user on the product detail interface is determined according to the acquired time. And then, judging whether the total residence time is greater than the second preset time threshold value. And if so, generating the target user behavior event. Namely, the server can also obtain the stay time sent by the client, so as to determine whether to generate the target user behavior event according to the stay time.

S703: and acquiring a sliding event of the user to the interface at the product detail interface.

S704: and generating a target user behavior event according to the sliding event.

The sliding event may carry a sliding proportion of the user to the interface, where the sliding proportion is greater than a preset proportion threshold. The preset proportion threshold value can be set according to actual conditions, such as 50%. Illustratively, when the user browses the product detail interface, the interface records the sliding proportion of the user to the interface, and determines whether the sliding proportion is greater than a certain proportion, for example, greater than the preset proportion threshold. And if the sliding proportion is larger than the preset proportion threshold, the client sends the sliding event to the server. And the server generates a target user behavior event according to the sliding event.

Here, the client sends the sliding event to the server only when the sliding proportion of the user is greater than a certain proportion, so that the accuracy of subsequent processing can be further improved. Because the sliding proportion of the user is larger than a certain proportion, the probability that the user needs to purchase the product subsequently is higher. And the server correspondingly generates the target user behavior event, so that the user data corresponding to the target user behavior event is obtained and cached. Therefore, when the user performs limited-time rush purchase on the product, the user can interact with the cache, and the stability of the server is improved.

As described above, the server may determine whether to acquire the sliding event for the first time when generating the target user behavior event according to the sliding event. For example, the sliding event carries an identifier of a user, and the server may determine whether to acquire the sliding event for the first time according to the identifier of the user and an acquired user identifier of the user in the sliding event of the product detail interface to the interface. If the sliding event is acquired for the first time, the server may generate the target user behavior event according to the sliding event, acquire user data corresponding to the target user behavior event, and cache the user data. When the user places an order again, the server can directly acquire corresponding user data from the cache, so that the pressure of a database on the server is reduced, and the user experience is also improved.

In addition, the server can also obtain the sliding proportion of the user on the interface of the product detail interface, which is periodically sent by the client, so that the total sliding proportion of the user on the interface of the product detail interface is determined according to the obtained sliding proportion, and whether the total sliding proportion is greater than the preset proportion threshold value is judged. And if so, generating the target user behavior event. Namely, the server can also obtain the sliding proportion sent by the client, so as to determine whether to generate the target user behavior event according to the sliding proportion.

Here, the server may generate the target user behavior event according to a variety of operations, for example, the server may generate the target user behavior event according to the stay event, or may generate the target user behavior event according to the slide event. Specifically, the target user behavior event generated according to which operation may be determined according to an actual situation.

S705: and writing the target user behavior event into a preset message queue.

S706: and acquiring user data corresponding to the target user behavior event in the preset message queue through at least one service interface.

The at least one service interface may include a user address service interface, and the user data may include a user address. The server may obtain the identifier of the user when obtaining the user data corresponding to the target user behavior event in the preset message queue through at least one service interface, and further obtain the user address corresponding to the identifier of the user through the user address service interface. The identifier of the user may be the uid of the user.

In addition, the at least one service interface may further include a user product service interface, and the user data may further include an order list. When the server obtains the user data corresponding to the target user behavior event in the preset message queue through at least one service interface, the server can obtain an order list corresponding to the user identifier through the user product service interface.

S707: and caching the user data.

According to the embodiment of the application, the server can generate the target user behavior event according to the stay event or the slide event, and further acquire the user data corresponding to the target user behavior event, and cache the user data, namely, the server actively caches the user data used by other post-positioned operations in advance. In this way, for some activities, such as a double eleven shopping activity, a new handset preemption activity, the server may actively cache data for users to participate. In the first moment of the robbery, the user interacts with the cache to complete the order, and the order cannot directly interact with the database, so that frequent access of the user to the database is reduced, and the stability of the server is improved.

Fig. 8 is a schematic structural diagram of a data caching device according to an embodiment of the present application, corresponding to the data caching method according to the foregoing embodiment. For convenience of explanation, only portions related to the embodiments of the present application are shown. Fig. 8 is a schematic structural diagram of a data caching apparatus according to an embodiment of the present application, where the data caching apparatus 80 includes: an event obtaining module 801, an event writing module 802, a data obtaining module 803, and a data caching module 804. The data caching device is applied to the order placing process of the user, and can be the server itself or a chip or an integrated circuit for realizing the functions of the server. It should be noted here that the division of the event obtaining module, the event writing module, the data obtaining module, and the data caching module is only a division of a logic function, and the two may be integrated or independent physically.

The event obtaining module 801 is configured to obtain a target user behavior event.

An event writing module 802, configured to write the target user behavior event into a preset message queue.

A data obtaining module 803, configured to obtain, through at least one service interface, user data corresponding to the target user behavior event in the preset message queue.

A data caching module 804, configured to cache the user data.

In one possible design, the event obtaining module 801 is specifically configured to:

acquiring a live broadcast service access interface calling request;

and generating the target user behavior event according to the calling request.

In a possible implementation manner, the event obtaining module 801 is specifically configured to:

determining whether to acquire the call request for the first time;

The data obtaining module 803 is further configured to obtain a service parameter of the live broadcast service according to the identifier of the live broadcast service after the event writing module 802 writes the target user behavior event into a preset message queue;

determining whether a shopping cart parameter exists in the service parameters;

The data obtaining module 803 is specifically configured to:

In one possible implementation manner, after caching the user data, the data caching module 804 is further configured to:

acquiring a stay event of a user on a product detail interface;

and generating the target user behavior event according to the stay event.

determining whether to acquire the stay event for the first time;

acquiring a sliding event of a user on the interface in a product detail interface;

and generating the target user behavior event according to the sliding event.

In a possible implementation manner, the sliding event carries a sliding proportion of the user to the interface, and the sliding proportion is greater than a preset proportion threshold.

determining whether to acquire the sliding event for the first time;

The data obtaining module 803 is specifically configured to:

acquiring the identification of the user;

The data obtaining module 803 is specifically configured to:

The apparatus provided in the embodiment of the present application may be configured to implement the technical solution of the method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again in the embodiment of the present application.

Optionally, fig. 9 schematically provides a possible basic hardware architecture of the data caching device described in the present application.

Referring to fig. 9, a data caching device 900 includes at least one processor 901 and a communication interface 903. Further optionally, a memory 902 and a bus 904 may also be included.

The data caching device 900 may be the server described above, and this application is not limited in this respect. In the data caching device 900, the number of the processors 901 can be one or more, and fig. 9 only illustrates one of the processors 901. Alternatively, the processor 901 may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or a Digital Signal Processing (DSP). If the data caching device 900 has multiple processors 901, the types of the multiple processors 901 may be different, or may be the same. Alternatively, the processors 901 of the data caching device 900 can also be integrated into a multi-core processor.

Memory 902 stores computer instructions and data; the memory 902 may store computer instructions and data necessary to implement the above-described data caching methods provided herein, e.g., the memory 902 stores instructions for implementing the steps of the above-described data caching methods. Memory 902 may be any one or any combination of the following storage media: nonvolatile memory (e.g., Read Only Memory (ROM), Solid State Disk (SSD), hard disk (HDD), optical disk), volatile memory.

The communication interface 903 may provide information input/output for the at least one processor. Any one or any combination of the following devices may also be included: a network interface (e.g., an ethernet interface), a wireless network card, etc. having a network access function.

Optionally, the communication interface 903 may also be used for data communication between the data caching device 900 and other computing devices or terminals.

Further alternatively, fig. 9 shows bus 904 with a thick line. The bus 904 may connect the processor 901 with the memory 902 and the communication interface 903. Thus, via bus 904, processor 901 may access memory 902 and may also interact with other computing devices or terminals using communication interface 903.

In this application, the data caching device 900 executes computer instructions in the memory 902, so that the data caching device 900 implements the data caching method provided in this application, or the data caching device 900 deploys the data caching apparatus.

From the viewpoint of logical functional division, illustratively, as shown in fig. 9, the memory 902 may include an event obtaining module 801, an event writing module 802, a data obtaining module 803, and a data caching module 804. The inclusion herein merely refers to that the instructions stored in the memory may, when executed, implement the functions of the event obtaining module, the event writing module, the data obtaining module and the data caching module, respectively, and is not limited to a physical structure.

In addition, the data caching device may be implemented by software as in fig. 8, or may be implemented by hardware as a hardware module or as a circuit unit.

The present application provides a computer-readable storage medium storing a computer program that causes a server to execute the above-described data caching method provided by the present application.

The present application provides a computer program product comprising computer instructions for executing the above data caching method provided by the present application by a processor.

The present application provides a chip comprising at least one processor and a communication interface providing information input and/or output for the at least one processor. Further, the chip may also include at least one memory for storing computer instructions. The at least one processor is used for calling and running the computer instructions to execute the data caching method provided by the application.

In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.

Claims

1. A method for caching data, the method comprising:

acquiring a target user behavior event;

writing the target user behavior event into a preset message queue;

and caching the user data.

2. The method of claim 1, wherein the obtaining a target user behavior event comprises:

acquiring a live broadcast service access interface calling request;

and generating the target user behavior event according to the calling request.

3. The method of claim 2, wherein generating the target user behavior event according to the invocation request comprises:

4. The method of claim 2, wherein generating the target user behavior event according to the invocation request comprises:

determining whether to acquire the call request for the first time;

5. The method according to any one of claims 2 to 4, wherein the invocation request carries an identification of the live service;

determining whether a shopping cart parameter exists in the service parameters;

6. The method of claim 5, wherein the invocation request further carries an identification of the user, wherein the at least one service interface includes a user address service interface, and wherein the user data includes a user address;

7. The method of claim 6, wherein the at least one service interface further comprises a user product service interface, the user data further comprises an order list;

8. The method of claim 6, further comprising, after said caching said user data:

9. The method of claim 1, wherein the obtaining a target user behavior event comprises:

acquiring a stay event of a user on a product detail interface;

and generating the target user behavior event according to the stay event.

10. The method of claim 9, wherein the dwell event carries a dwell time of the user at the product detail interface, the dwell time being greater than a second preset time threshold.

11. The method of claim 9, wherein generating the target user behavior event according to the dwell event comprises:

determining whether to acquire the stay event for the first time;

12. The method of claim 1, wherein the obtaining a target user behavior event comprises:

acquiring a sliding event of a user on a product detail interface;

and generating the target user behavior event according to the sliding event.

13. The method of claim 12, wherein the slide event carries a slide proportion of the user at the product detail interface, the slide proportion being greater than a preset proportion threshold.

14. The method of claim 12, wherein generating the target user behavior event according to the sliding event comprises:

determining whether to acquire the sliding event for the first time;

15. The method according to any of claims 9 to 14, wherein the at least one service interface comprises a user address service interface, the user data comprising a user address;

acquiring the identification of the user;

16. The method of claim 15, wherein the at least one service interface further comprises a user product service interface, the user data further comprises an order list;

17. A data caching apparatus, comprising:

the event obtaining module is used for obtaining a target user behavior event;

and the data caching module is used for caching the user data.

18. A data caching apparatus, comprising:

a processor;

a memory; and

a computer program;

wherein the computer program is stored in the memory and configured to be executed by the processor, the computer program comprising instructions for performing the method of any of claims 1-16.

19. A computer-readable storage medium, characterized in that it stores a computer program that causes a server to execute the method of any of claims 1-16.

20. A computer program product comprising computer instructions for executing the method of any one of claims 1 to 16 by a processor.