CN118503295B - Service processing method and service processing device - Google Patents

Abstract

The present disclosure provides a service processing method and a service processing device, which are applied to the field of computers, and the method includes: receiving a first query request sent by a first terminal; determining query target information according to the first query request, and determining whether the query target information meets a first condition; if the query target information meets the first condition, acquiring first data from the cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from the service system according to the query target information, and determining the query result according to the first data and the second data; if the query target information does not meet the first condition, third data are acquired from the service system according to the query target information, and a query result is determined. Therefore, the time consumption of query waiting of a user and the request call quantity of a service system are reduced, and the normal display of data in abnormal conditions is ensured.

Description

Service processing method and service processing device

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a service processing method and a service processing device.

Background

In the prior art, digitization is a transformation direction of a business processing platform in the financial industry, along with the continuous expansion of personal businesses, the number of users in the personal channels is obviously increased, and in order to meet the requirements of different guest groups, various asset services are continuously online, for example, mobile banking provides aggregation query functions of various businesses, assets, benefits and the like. The service scene has the characteristics of higher timeliness and concurrency, so a processing method is needed to be provided, and the problems of slow data query and error of query results caused by the characteristics of large concurrency demand, high real-time dependence and strong data relevance of the service scene are solved.

Disclosure of Invention

The present disclosure provides a service processing method, a service processing device, an electronic apparatus, and a storage medium, so as to at least solve the above technical problems in the prior art.

In a first aspect, an embodiment of the present disclosure provides a service processing method, where the method includes:

receiving a first query request sent by a first terminal;

determining query target information according to the first query request, and determining whether the query target information meets a first condition;

If the query target information meets a first condition, acquiring first data from a cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from a service system according to the query target information, and determining the query result according to the first data and the second data;

If the query target information does not meet the first condition, third data are acquired from a service system according to the query target information, and a query result is determined according to the third data;

And sending the query result to the first terminal.

In a second aspect, an embodiment of the present disclosure provides a service processing apparatus, including:

The receiving module is used for receiving a first query request sent by the first terminal;

The first processing module is used for determining query target information according to the first query request and determining whether the query target information meets a first condition;

If the query target information meets a first condition, acquiring first data from a cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from a service system according to the query target information, and determining the query result according to the first data and the second data;

If the query target information does not meet the first condition, third data are acquired from a service system according to the query target information, and a query result is determined according to the third data;

and the sending module is used for sending the query result to the first terminal.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including:

At least one processor; and

A memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the methods described in the present disclosure.

In a fourth aspect, the disclosed embodiments provide a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the methods described in the disclosure.

The embodiment of the disclosure provides a service processing method, a service processing device, an electronic device and a storage medium, wherein the method comprises the following steps: receiving a first query request sent by a first terminal; determining query target information according to the first query request, and determining whether the query target information meets a first condition; if the query target information meets a first condition, acquiring first data from a cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from a service system according to the query target information, and determining the query result according to the first data and the second data; if the query target information does not meet the first condition, third data are acquired from a service system according to the query target information, and a query result is determined according to the third data; and sending the query result to the first terminal. Therefore, the query from the cache cluster and the query from the service system are combined, so that the time consumption for waiting for the query of the user is greatly reduced, the service is decoupled, the request call quantity of the service system is reduced, and the normal display of the data in abnormal conditions is ensured.

It should be understood that the description in this section is not intended to identify key or critical features of the embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become apparent from the following specification.

Drawings

Fig. 1 is a schematic flow chart of a service processing method according to an embodiment of the disclosure;

fig. 2 is a flow chart of a data updating method provided by an embodiment of the disclosure;

Fig. 3 is a flow chart of another data linkage updating method provided by an embodiment of the disclosure;

Fig. 4 is a schematic diagram of a data cache cluster provided by an embodiment of the disclosure;

fig. 5 is a flow chart of a service processing method provided by an embodiment of the disclosure;

Fig. 6 is a schematic structural diagram of a service processing device according to an embodiment of the present disclosure;

Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.

Detailed Description

In order to make the objects, features and advantages of the present disclosure more comprehensible, the technical solutions in the embodiments of the present disclosure will be clearly described in conjunction with the accompanying drawings in the embodiments of the present disclosure, and it is apparent that the described embodiments are only some embodiments of the present disclosure, but not all embodiments. Based on the embodiments in this disclosure, all other embodiments that a person skilled in the art would obtain without making any inventive effort are within the scope of protection of this disclosure.

Fig. 1 is a flow chart of a service processing method according to an embodiment of the present disclosure, as shown in fig. 1, where the method includes:

step 101, receiving a first query request sent by a first terminal;

Step 102, determining query target information according to the first query request, and determining whether the query target information meets a first condition;

Step 103, if the query target information meets a first condition, acquiring first data from a cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from a service system according to the query target information, and determining the query result according to the first data and the second data;

104, if the query target information does not meet the first condition, acquiring third data from a service system according to the query target information, and determining a query result according to the third data;

Step 105, sending the query result to the first terminal.

In some embodiments, the method is applied to an electronic device, which may be a device having data processing, data interaction, etc., for example, the electronic device may be a computer, a server, etc.

The electronic device may comprise a service processing module for executing the service processing method.

In some embodiments, the first terminal is a terminal held by a user, and the user may operate through a human-computer interaction interface provided by the first terminal to input the first query request.

Specifically, the first terminal may be provided with a client, through which interaction with the electronic device is performed, and the client may be, for example, a mobile phone Application APP (Application).

Receiving a first query request sent by a first terminal, including: and receiving a first query request sent by a client of the first terminal.

The first query request can be used for querying any service, and can also be used for querying asset data and the like corresponding to the service of the user; for example, the first inquiry request is a request to inquire about a deposit situation, a request to inquire about a financial situation, or the like.

In some embodiments, the cache cluster comprises: a first cache set and a second cache set;

The first cache set includes product asset data for each of at least one business and an update timestamp for the product asset data;

the second cache set includes personal asset data for each of at least one user and an update timestamp for the personal asset data.

Here, the service and the user stored in the cache cluster are the service and the user with the cache authority, the service with the cache authority is marked as the first type of service, and the user with the cache authority is marked as the first type of user; and the service without the caching authority is marked as a second-class service, and the user without the caching authority is marked as a second-class user.

In some embodiments, the determining query target information according to the first query request, determining whether the query target information meets a first condition includes:

determining query target information according to the first query request, wherein the query target information comprises: target users and target services;

Determining whether the query target information meets a first condition according to a preset service processing rule, the target user and a target service;

correspondingly, the query target information meets a first condition, including:

Determining that a target user is a first type user and the target service is a first type service according to the preset service processing rule;

the query target information does not satisfy a first condition, including at least one of:

determining that the target service is a second type service according to the preset service processing rule;

determining that the target service is a first type service or a second type service according to the preset service processing rule, and the target user is a second type user;

the preset business processing rule is used for indicating at least one first type business and/or at least one first type user;

the first type of service is a service in which product asset data is stored in the cache cluster;

the first type of users are users with personal asset data stored in the cache cluster.

Specifically, the target query information includes:

The target user can adopt unique identity identification representation of the user;

The target service can be represented by a service name, a service number and the like.

Specifically, the preset service processing rule is used for indicating at least one first type service and/or at least one first type user; for example, the preset business processing rule indicates the following information:

the first service, the second service, the third service and the like are the first type of service;

Service IV, service V, etc., are second kind of service;

the first user, the second user, the third user and the like are the first type of users;

user four, user five, etc., are second class users.

For example, the first type of traffic is traffic that can be buffered, such as: funds, financing, trust, deposit, insurance, electronic national debt, precious metal, commercial endowment insurance;

The second type of service is a real-time query service, such as: direct marketing, counter debt, credit card, loan, personal care, etc.

Of course, the preset service processing rule may be set based on the user, the service, etc. involved in the actual application scenario, which is not limited herein.

After determining the query target information (including the target user and the target service) according to the first query request, judging whether the query target information meets a first condition according to a preset service processing rule.

Here, it is determined whether the query target information satisfies a first condition, that is, whether the data of the query requested by the first query request is obtained from the cache cluster or from the service system.

If the query target information does not meet the first condition, the query data requested by the first query request can be determined to be acquired from the service system, so that third data can be acquired from the service system according to the query target information, and a query result is determined according to the third data;

If the query target information meets the first condition, it can be determined that the query data requested by the first query request can be obtained from the cache cluster, so that the first data can be obtained from the cache cluster according to the query target information, and then the query result is determined.

In some embodiments, the first data comprises: product data and user data, said determining whether said first data meets a second condition, comprising:

determining a first update time corresponding to the user data;

Determining a second update time corresponding to the product data;

Determining a precedence relationship between the first update time and the second update time;

accordingly, the first data satisfies a second condition, including: the first update time is a time after the second update time;

the first data does not satisfy a second condition, comprising: the first update time is a time before the second update time.

Specifically, when data is acquired from the cache clusters, the client-level cache data (i.e., user data) and the product-level cache data (i.e., product data) may be acquired simultaneously.

The cache data of the product level is correspondingly provided with (or comprises) a time stamp for issuing or updating;

The client-level cache data is correspondingly provided with (or comprises) a time stamp for issuing or updating;

And comparing the time information of the cache data of the product level with the time information of the cache data of the client level to determine whether the data acquired from the cache cluster is valid or not or whether the data is in doubt, and if the data is invalid or in doubt, acquiring real-time data from a service system to ensure the accuracy of the data.

In some embodiments, the determining whether the first data satisfies a second condition further comprises:

Determining whether the user data corresponds to a failure tag;

correspondingly, the first data meets the second condition, and further comprises: the user data does not correspond to an invalidation tag;

the first data does not satisfy the second condition, further comprising: the user data corresponds to a failure tag.

Specifically, when the user data in the cache cluster is adopted as a result, timeliness of the user data needs to be considered, in practical application, an invalidation tag can be added to the user data according to specific conditions, and if the user data corresponds to the invalidation tag, the user data in the current cache cluster is considered to be suspicious or possibly abnormal.

The invalidation tag is a tag added in the process of updating the user data and is used for reflecting whether the current data is suspicious or possibly abnormal.

Here, the update time and the tag may be combined to determine, and if the time of the product level (i.e., the second update time) is newer, the cache data is considered to be invalid, and the asset data is queried and compared again through the real-time interface.

If the client-level data (i.e. the second update time) is newer, the method is further divided into two cases, and specifically, whether the client-level data is a stage one is needed to be judged, wherein the stage one is a stage in which the cache data is marked as invalid and the latest data is not asynchronously refreshed and written, and if the cache data is invalid, the latest data is acquired from a service system through a real-time interface; if not, the cache data is considered to be valid, and the cache data in the cache cluster is directly read.

In some embodiments, the obtaining second data from the service system according to the query target information, determining a query result according to the first data and the second data, includes:

Determining a first service system according to the query target information;

sending a second query request to the first service system through a real-time interface, wherein the second query request is used for requesting the first service system to feed back the latest data of the target user;

receiving second data sent by the first service system, wherein the second data comprises the latest data of a target user;

And determining a query result according to the first data and the second data.

Specifically, the query target information further includes: a first tag and a second tag;

The first tag is used for marking a data source, and the data source can be a service system for generating data;

The second tag is used to mark a data type, which can be used to distinguish between a customer and a business, if the customer indicates that the data is customer asset change data, if the business indicates that the data is business corresponding product asset change data. If the customer is a client, the customer can be further specifically classified into deposit, financial, total asset and other specific types.

Here, determining the first service system according to the query target information includes:

determining a first label according to the query target information;

and determining a first service system corresponding to the first label according to the first relation table.

The first relation table is preset and stored in the electronic equipment, and comprises at least one label and a service system corresponding to each label. The business system may include: a replacement marketing system, a core system, etc. For example, the sales substituting system may be a system for substituting for some financial resource, and the core system may be a system for performing sum processing such as data settlement by a bank.

Here, the first service system is provided with a real-time interface, and the service processing module can send a request to the first service system through the real-time interface and receive the feedback result in real time, so that a second query request can be sent to the first service system through the real-time interface, wherein the second query request carries a user identifier and a specific category so as to inform the first service terminal of a user specifically required to be queried and the content of the required query.

In some embodiments, the method further comprises:

if second data fed back by the first service system are received, determining a first update request according to the second data;

and sending a first updating request to the cache cluster, wherein the first updating request is used for requesting the cache cluster to update the user data corresponding to the target user.

If the second query request is sent to the first service system, it indicates that the data in the cache cluster is considered to be in doubt, so that when the latest data (i.e., the second data) fed back in real time by the first service system is received, a first update request containing or carrying the second data is sent to the cache cluster, so that the cache cluster updates the user data corresponding to the target user according to the second data.

And when updating, updating the time stamp for the updated user data, which is used for reflecting the timeliness of the updated data, so that whether the user data is suspicious or usable can be determined according to the time stamp in the subsequent inquiry.

In some embodiments, the method further comprises:

Receiving data change information sent by a second service system, wherein the data change information comprises: user change data and/or business change data;

according to a preset service processing rule, determining the change data of the first type of service and/or the change data of the first type of user in the data change information;

If the data change information comprises change data of a first type of service, updating product asset information corresponding to the service in the cache cluster according to the change data of the first type of service;

If the data change information comprises change data of a first type of users, a first failure instruction is sent to the cache cluster; asynchronous refreshing is carried out according to the user identification of the first type user and the change data of the first type user, and an asynchronous refreshing result is obtained; updating personal asset information corresponding to a user in the cache cluster according to the asynchronous refreshing result, and deleting an invalidation tag; the first invalidation instruction is used for indicating the cache cluster to add invalidation labels to the user data.

In some embodiments, asynchronous refreshing is performed according to the user identifier of the first type of user and the change data of the first type of user, to obtain an asynchronous refreshing result, including:

Determining a service type and at least one third service system corresponding to the change data according to the change data of the first type of users;

Sending a second updating request to each third service system according to the user identification of the first type of users so as to carry out asynchronous refreshing;

receiving an asynchronous refreshing result fed back by each third service system, and updating personal asset information corresponding to a user in the cache cluster according to the asynchronous refreshing result corresponding to each service type;

And/or the number of the groups of groups,

And receiving asset updating data sent by a fourth service system, and updating personal asset information corresponding to the user in the cache cluster according to the asset updating data.

Specifically, the second service system may actively send data change information, and after the service processing module receives the data change information, the data in the cache cluster needs to be updated according to the data change information.

Here, the preset service processing rule is used for indicating at least one first type service and/or at least one first type user;

after receiving the data change message, each user and/or service included in the data change message is respectively matched with the first type service and the first type user indicated in the preset service processing rule, and whether the data change message contains change data of the first type service or not is determined, and whether the data change message contains change data of the first type user or not is determined.

Updating product asset information corresponding to the business in the cache cluster according to the change data of the first type of business aiming at the change data of the first type of business included in the data change information; and, the time stamp of the product asset information is updated.

For the change data of the first type of users included in the data change information, user data update in the cache cluster is divided into a plurality of stages, and each stage represents the invalidation or update of a part of data. Specifically, the method comprises the following steps: sending a first invalidation instruction to the cache cluster to set invalidation of user data related to variable data; simultaneously, asynchronous refreshing is carried out according to the user identification of the first type of users and the change data of the first type of users, and an asynchronous refreshing result is obtained; and updating the personal asset information corresponding to the user in the cache cluster according to the asynchronous refreshing result, deleting the failure tag, and updating the time stamp of the personal asset information. Therefore, the situation of data feedback errors caused by the fact that a user inquires related data in the data updating process is avoided.

By the method, specific business processing logic and client access are isolated, so that black box access of data is realized; and the influence of the abnormality of the service system on the whole service is reduced through the service processing module and the cache cluster. Compared with a multi-thread concurrent query service system, the method provided by the embodiment of the disclosure directly reads the cache cluster when a user requests relevant holding asset data, and combines a small part of real-time data, so that interaction between the user and a specific service system is reduced, query efficiency is improved, and user experience is improved.

There is provided an application embodiment, as shown in fig. 2, the data updating method, including:

When the related data of the asset changes, the business system sends the data change information to the business processing module through the first message queue; wherein, the business system includes: core system, expense system, etc., the expense system is such as the system of business such as financial accounting, fund, etc.;

the business processing module performs data cleaning on the user change data and/or business change data in the data change information based on the first data cleaning rule;

in the data cleaning process, the type judgment is carried out according to the fluctuation data of the user and/or the fluctuation data of the service, and the first operation or the second operation is executed according to the judgment result so as to update the data in the cache cluster.

The cache cluster adopts an HBASE (Hadoop Database, a distributed storage system) cluster. The HBASE cluster includes: product cache (corresponding to an example of a first cache set), user cache (corresponding to an example of a second cache set).

Wherein the first operation comprises:

For the business change data, sending the business change data to a relational database service (RDS, relational Database Service) platform through a second message queue, and sending the business change data to a cache cluster through the RDS platform; and the cache cluster updates the product asset information corresponding to the business according to the change data of the business.

And asynchronous refreshing is carried out according to the fluctuation data of the user and the business system, and the personal asset information corresponding to the user in the cache cluster is updated according to the asynchronous refreshing result.

Wherein, the first message queue can adopt SofaMQ middleware, a distributed message middleware; the second message queue may employ Kafka middleware, a distributed publish-subscribe messaging system.

Regarding asynchronous refreshing in combination with a service system, updating personal asset information corresponding to a user in a cache cluster according to an asynchronous refreshing result, and providing a specific application embodiment, as shown in fig. 3, taking the service system as an example, including a proxy system and a core system, the data linkage updating method includes:

The trading system financing trading batch generates a trading file and sends the trading file to the core system;

The core system modifies customer accounts in batches according to the transaction files, generates account checking files after batch running is finished, and sends the account checking files to the sales system;

Meanwhile, after the customer accounts are modified in batches, data change information is generated, and the data change information is sent to a service processing module through a first message queue (such as SofaMQ middleware); the data change information includes: the change data of the user, specifically, deposit data, the corresponding first label can be a core system, and the second label can be deposit;

The business processing module carries out data cleaning on the change data of the user based on a first data cleaning rule, and determines that deposit data is changed in the data cleaning process, then a first invalidation instruction is sent to the cache cluster through a second message queue (such as Kafka middleware) and an RDS platform, and the first invalidation instruction is used for indicating the cache cluster to add invalidation labels for the user data or indicates the cache cluster to add invalidation labels for deposit data and financial data in the user data; marking invalidation of the cache cluster according to a first invalidation instruction;

Meanwhile, the asynchronous refresh one operation is performed, including: sending a second update request to the core system to perform asynchronous refreshing; receiving an asynchronous refreshing result fed back by a core system, wherein the asynchronous refreshing result comprises the latest deposit data; updating deposit asset caches in the personal asset information corresponding to the users in the cache cluster according to the latest deposit data;

In the above process, the sales substituting system updates the asset, and after updating, the sales substituting system actively sends data change information to the service processing module, where the data change information includes: the change data of the user, specifically financial data, the corresponding first label can be a sales substituting system, and the second label can be financial data; and after receiving the financial data, the service processing module performs data cleaning based on a second data cleaning rule and executes asynchronous refreshing operation II, and the service processing module comprises the following steps: sending a second update request to the sales replacement system to perform asynchronous refreshing; receiving asynchronous refreshing results fed back by the sales substituting system, wherein the asynchronous refreshing results comprise the latest financial data; and updating financial asset caches in the personal asset information corresponding to the users in the cache cluster according to the latest financial data.

Therefore, the cache preheating capability is provided, in order to optimize the waiting experience when the user accesses, the detail data in the holding data are asynchronously refreshed through a data cleaning link in the message pushing, and the latest data are directly displayed after the interface accesses the request through an external real-time interface.

The business processing module recognizes that corresponding asset data is changed in a data cleaning link, firstly sets a timestamp mark in a cache cluster as invalid in real time, and then calls a real-time interface to acquire the latest user data and refresh the cache, thereby improving the waiting experience of user access and ensuring the accuracy of the data.

By the method provided by the embodiment of the disclosure, the consistency of all data is ensured, the influence of data inconsistency caused by message link delay is reduced, and the consistency of data display is ensured by binding and associating the associated service data in the processing logic segment with invalid data cache.

Specifically, the data change information includes specially marked tags (such as the first tag and the second tag), for example, the transaction data pushing of financial transaction is delayed and has a time difference with the account dynamic account pushing data in the core system, when the identification tag determines that the data type of the data change information is deposit, deposit holding cache data is set to be in an expiration state, and meanwhile, financial holding cache data is also set to be verified (namely, stage one, stage two and stage three in the figure are used for explaining the failure or update of part of the data), if a user logs in to access and requests to inquire deposit and financial transaction during the period, the situation that the cache data is in doubt exists is existed, here, through switching to an operation of real-time inquiry (namely, an asynchronous refreshing operation), until message pushing of a proxy system and the core system is received, the pushed accurate data is fed back to the user, and refreshing of the cache data is completed (namely, updating of stage two and stage three is completed). The situation that the data in the latest cache data acquired from the cache cluster is abnormal data (at the moment, deposit in the cache data is correct data and financial is error data) because the pushing of financial is not sent out during the stage two access of the user is avoided.

Thus, the cache data in the cache cluster and the real-time data in the service system are jointly processed, the cache cluster is combined without inquiring the data from the service system every time, so that the time consumption for inquiring the user is greatly reduced, and taking a financial heavy-warehouse holding client as an example, the time consumption for inquiring the asset can be reduced from more than 2 seconds to less than 500 milliseconds and reduced by 75 percent; in addition, service decoupling is realized, a back-end service system is protected, the request call quantity of the back-end service system can be reduced by about 70%, and normal display of data in abnormal conditions is ensured; in addition, the throughput (TPS, transactions Per Second) of the server is improved, the hardware resource requirement is reduced, the throughput of a single server can be improved by about 58% after a scheme of combining caching and real-time is used, and the budget requirement of capacity expansion is reduced.

Fig. 4 is a schematic diagram of a cache cluster provided by an embodiment of the disclosure; as shown in fig. 4, the cache cluster includes: a first cache set and a second cache set;

The first cache set includes product asset data for each of at least one business and an update timestamp for the product asset data;

the second cache set includes personal asset data for each of at least one user and an update timestamp for the personal asset data.

For example, the personal asset data of user a includes: asset a, asset B, and timestamps corresponding to asset a, asset B;

The personal asset data of user B includes: asset a, asset B, and the time stamps corresponding to asset a, asset B.

Different assets of the same user may correspond to different timestamps, respectively, i.e., asset a may correspond to a first timestamp representing an update time of asset a and asset B may correspond to a second timestamp representing an update time of asset B.

As another example, the different services may include: net value type, share type, real-time estimation, etc.;

Wherein the equity product asset data comprises: net value, type, release day; for example, the type may be a financial product such as a fund, with the net value being that of the corresponding fund;

Product asset data of the share type, comprising: share type, publication day; for example, a share type may be a product of a business such as a inventory, corresponding to its particular share;

Product asset data for real-time valuation, comprising: category-each value, release day; for example, a category may be such as gold price, exchange rate, etc., with each value representing a real-time estimate of the category.

The product asset data for different types of business may be different, with the release date representing the update time of the product asset data.

In practical application, the asset data of each user can be calculated by combining the above services and the asset information of the user, for example, the asset a of the user a is an asset estimated in real time, the asset a includes the number of possession, and the amount of the asset a of the user a can be obtained according to the real-time estimated and the number of possession.

Here, the cache data in the cache cluster can be used as response content, the data stored in the cache module is used as response content, the two dimensions of the asset and the client are used for dividing, and when the access is requested, the corresponding cache data is provided, so that the coupling degree with the service system is reduced, and the response efficiency is improved.

In a cache cluster, data is divided into two dimensions, product level and user level, wherein,

The data source of the product dimension cache depends on the part forwarded by Kafka in the message push link, and the expired data is marked and refreshed through a standardized data template by release date, update time stamp and the like;

The data source of the user dimension cache is based on a real-time query result in the data processing service, and when the corresponding asset change is identified in the data cleaning link, the corresponding service system is requested to acquire the correct user asset data in a delay interface query mode and written into the cache. Meanwhile, the update time of the cache is marked by the timestamp, and when a user accesses, the specific cache effective timestamp can be compared to avoid the influence of dirty data with invalid cache.

In the service processing module, the switching between the query cache and the real-time link can be realized, and the combined configuration operation is pointed out, for example, funds and financial resources can be set, and the actual asset data of the user can be obtained through the cache and the real-time data interface respectively. When the user accesses, the business processing module performs data combination and provides corresponding asset data as a query result.

Fig. 5 is a schematic structural diagram of a service processing method provided by an embodiment of the application of the present disclosure; as shown in fig. 5, the method is applied to a service processing module in the electronic device; the service processing module can receive a query request sent by the mobile banking APP and can interact with the service system through a real-time interface.

The service processing method of the service processing module comprises the following steps:

Receiving a personal asset inquiry request and judging whether a first condition is met or not; specifically, query target information is determined according to a personal asset query request (an example of a first query request), and whether the query target information meets a first condition is determined;

If the first condition is met, the first data is considered to belong to a cache group, and the first data is acquired from an HBASE cluster (an example of a cache cluster); judging whether the first data meets the second condition, if so, considering that the acquired data is effective to acquire, and executing a third operation; and if the second condition is not met, the acquired data is considered to be invalid, and the data refreshing operation is executed. Here, the data refreshing operation is used to refresh asset data with invalid cache and doubtful data, and the data refreshing operation includes: second data is acquired from the core and the proxy marketing system (an example of a business system) to acquire the latest asset data through a real-time interface provided by the core and the proxy marketing system, and the user cache data in the HBASE cluster is updated asynchronously. Here, the third operation includes: and carrying out data combination calculation according to the first data, and feeding back the query result to the client through the mobile banking APP.

If the first condition is not met, the mobile phone bank APP is considered to belong to the real-time group, third data are acquired from the core and the sales substituting system, data combination calculation is carried out according to the third data, and after the query result is determined, the query result is fed back to the client through the mobile phone bank APP.

Specifically, the HBASE cluster may include: caching products and users; the first data or the third data acquired therefrom may include: product asset data and personal asset data.

The data combination calculation includes calculation according to product asset data and personal asset data, the calculation rule can be preset and stored, different calculation modes can be set for each service, for example, precious metal service can be combined with real-time exchange rate, gold price and the like, and real-time asset data acquired in a service system can be accumulated after calculation, so that a final inquiry result of the personal asset can be obtained.

Fig. 6 is a schematic structural diagram of a service processing device according to an embodiment of the present disclosure; as shown in fig. 6, the apparatus includes:

The receiving module is used for receiving a first query request sent by the first terminal;

The first processing module is used for determining query target information according to the first query request and determining whether the query target information meets a first condition;

If the query target information meets a first condition, acquiring first data from a cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from a service system according to the query target information, and determining the query result according to the first data and the second data;

If the query target information does not meet the first condition, third data are acquired from a service system according to the query target information, and a query result is determined according to the third data;

and the sending module is used for sending the query result to the first terminal.

In some embodiments, the first processing module is configured to determine query target information according to the first query request, where the query target information includes: target users and target services;

Determining whether the query target information meets a first condition according to a preset service processing rule, the target user and a target service;

correspondingly, the query target information meets a first condition, including:

Determining that a target user is a first type user and the target service is a first type service according to the preset service processing rule;

the query target information does not satisfy a first condition, including at least one of:

determining that the target service is a second type service according to the preset service processing rule;

determining that the target service is a first type service or a second type service according to the preset service processing rule, and the target user is a second type user;

the preset business processing rule is used for indicating at least one first type business and/or at least one first type user;

the first type of service is a service in which product asset data is stored in the cache cluster;

the first type of users are users with personal asset data stored in the cache cluster.

In some embodiments, the first data comprises: the first processing module is used for determining a first updating time corresponding to the user data;

Determining a second update time corresponding to the product data;

Determining a precedence relationship between the first update time and the second update time;

accordingly, the first data satisfies a second condition, including: the first update time is a time after the second update time;

the first data does not satisfy a second condition, comprising: the first update time is a time before the second update time.

In some embodiments, the first processing module is further configured to determine whether the user data corresponds to a failure tag;

accordingly, the first data satisfies a second condition, including: the user data does not correspond to an invalidation tag;

the first data does not satisfy a second condition, comprising: the user data corresponds to a failure tag.

In some embodiments, the first processing module is configured to determine a first service system according to the query target information;

sending a second query request to the first service system through a real-time interface, wherein the second query request is used for requesting the first service system to feed back the latest data of the target user;

receiving second data sent by the first service system, wherein the second data comprises the latest data of a target user;

And determining a query result according to the first data and the second data.

In some embodiments, the first processing module is further configured to determine, if second data fed back by the first service system is received, a first update request according to the second data;

the sending module is further configured to send a first update request to the cache cluster, where the first update request is used to request the cache cluster to update user data corresponding to the target user.

In some embodiments, the receiving module is further configured to receive data change information sent by the second service system, where the data change information includes: user change data and/or business change data;

the first processing module is further configured to determine, according to a preset service processing rule, change data of a first type of service and/or change data of a first type of user in the data change information;

If the data change information comprises change data of a first type of service, updating product asset information corresponding to the service in the cache cluster according to the change data of the first type of service;

If the data change information comprises change data of a first type of users, a first invalidation instruction is sent to the cache cluster, asynchronous refreshing is carried out according to the user identification of the first type of users and the change data of the first type of users, and an asynchronous refreshing result is obtained; updating personal asset information corresponding to a user in the cache cluster according to the asynchronous refreshing result, and deleting an invalidation tag; the first invalidation instruction is used for indicating the cache cluster to add invalidation labels to the user data.

In some embodiments, the first processing module is configured to determine, according to change data of the first type of user, a service type and at least one third service system corresponding to the change data;

The sending module is used for sending a second updating request to each third service system according to the user identification of the first user so as to carry out asynchronous refreshing;

The receiving module is used for receiving the asynchronous refreshing result fed back by each third service system; the first processing module is used for updating the personal asset information corresponding to the user in the cache cluster according to the asynchronous refreshing result corresponding to each service type;

And/or the number of the groups of groups,

The receiving module is used for receiving the asset updating data sent by the fourth service system; and the first processing module is used for updating the personal asset information corresponding to the user in the cache cluster according to the asset updating data.

In some embodiments, the cache cluster comprises: a first cache set and a second cache set;

The first cache set includes product asset data for each of at least one business and an update timestamp for the product asset data;

the second cache set includes personal asset data for each of at least one user and an update timestamp for the personal asset data.

It will be appreciated that, when implementing the corresponding service processing method, the service processing apparatus provided in the foregoing embodiment may allocate the foregoing processing to be completed by different program modules according to need, so as to complete all or part of the processing described above. In addition, the apparatus provided in the foregoing embodiments and the embodiments of the corresponding methods belong to the same concept, and specific implementation processes of the apparatus and the embodiments of the methods are detailed in the method embodiments, which are not described herein again.

The embodiments of the present disclosure provide a computer readable storage medium having stored therein executable instructions that, when executed by a processor, will trigger the processor to perform the business processing method provided by the embodiments of the present disclosure.

In some embodiments, the computer readable storage medium may be ferroelectric random access Memory (Ferroelectric RAM, FRAM), read-Only Memory (ROM), programmable Read-Only Memory (Programmable Read-Only Memory, PROM), erasable programmable Read-Only Memory (Erasable Programmable ROM, EPROM), electrically erasable programmable Read-Only Memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory, EEPROM), flash Memory, magnetic surface Memory, optical disk, or CD-ROM; but may be a variety of devices including one or any combination of the above memories.

In some embodiments, the executable instructions may be in the form of programs, software modules, scripts, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and they may be deployed in any form, including as stand-alone programs or as modules, models, subroutines, or other units suitable for use in a computing environment.

As an example, executable instructions may be deployed to be executed on one computing device or on multiple computing devices located at one site or distributed across multiple sites and interconnected by a communication network.

Embodiments of the present disclosure provide a computer program product comprising computer programs/instructions which, when executed by a processor, implement the business processing methods described in the present disclosure.

Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure; as shown in fig. 7, the electronic device 70 includes: a processor 701 and a memory 702 for storing a computer program capable of running on the processor; the processor 701 is configured to execute the service processing method provided by the embodiment of the present disclosure when executing the computer program.

In practical applications, the electronic device 70 may further include: at least one network interface 703. The various components in the electronic device 70 are coupled together by a bus system 704. It is appreciated that bus system 704 is used to enable connected communications between these components. The bus system 704 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration, the various buses are labeled as bus system 704 in fig. 7. The number of the processors 701 may be at least one. The network interface 703 is used for wired or wireless communication between the electronic device 70 and other devices.

The memory 702 in the disclosed embodiments is used to store various types of data to support the operation of the electronic device 70.

The methods disclosed in the embodiments of the present disclosure may be applied to the processor 701 or implemented by the processor 701. The processor 701 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in the processor 701 or by instructions in the form of software. The Processor 701 may be a general purpose Processor, a digital signal Processor (DSP, diGital Signal Processor), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like. The processor 701 may implement or perform the methods, steps, and logic blocks disclosed in embodiments of the present disclosure. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present disclosure may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in the decoded processor. The software modules may be located in a storage medium in a memory 702. The processor 701 reads information in the memory 702 and, in combination with its hardware, performs the steps of the method as described above.

In some embodiments, the electronic device 70 may be implemented by one or more Application Specific Integrated Circuits (ASICs), DSPs, programmable logic devices (PLDs, programmable Logic Device), complex Programmable logic devices (CPLDs, complex Programmable Logic Device), field-Programmable gate arrays (FPGAs), general purpose processors, controllers, microcontrollers (MCUs, micro Controller Unit), microprocessors (microprocessors), or other electronic elements for performing the foregoing methods.

It should be appreciated that various forms of the flows shown above may be used to reorder, add, or delete steps. For example, the steps described in the present disclosure may be performed in parallel, sequentially, or in a different order, so long as the desired result of the technical solution of the present disclosure is achieved, and the present disclosure is not limited herein.

In the above description reference has been made to "some embodiments" which describe a subset of all possible embodiments, but it is to be understood that "some embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with each other without conflict.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. The terminology used in the present disclosure is for the purpose of describing embodiments of the present disclosure only and is not intended to be limiting of the present disclosure.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present disclosure, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.

The foregoing is merely specific embodiments of the disclosure, but the protection scope of the disclosure is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the disclosure, and it is intended to cover the scope of the disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims (7)

1. A method of service processing, the method comprising:

receiving a first query request sent by a first terminal;

determining query target information according to the first query request, and determining whether the query target information meets a first condition;

If the query target information meets a first condition, acquiring first data from a cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from a service system according to the query target information, and determining the query result according to the first data and the second data;

If the query target information does not meet the first condition, third data are acquired from a service system according to the query target information, and a query result is determined according to the third data;

sending the query result to the first terminal;

Wherein the determining query target information according to the first query request, determining whether the query target information meets a first condition, includes:

determining query target information according to the first query request, wherein the query target information comprises: target users and target services;

Determining whether the query target information meets a first condition according to a preset service processing rule, the target user and a target service;

correspondingly, the query target information meets a first condition, including:

Determining that a target user is a first type user and the target service is a first type service according to the preset service processing rule;

the query target information does not satisfy a first condition, including at least one of:

determining that the target service is a second type service according to the preset service processing rule;

determining that the target service is a first type service or a second type service according to the preset service processing rule, and the target user is a second type user;

the preset business processing rule is used for indicating at least one first type business and/or at least one first type user;

The first type of service is a service with a cache authority;

the first type of users are users with caching authority;

the second type of service is a service without caching authority;

The second class of users are users without caching rights;

Wherein the first data includes: product data and user data, said determining whether said first data meets a second condition, comprising:

determining a first update time corresponding to the user data;

Determining a second update time corresponding to the product data;

Determining a precedence relationship between the first update time and the second update time;

accordingly, the first data satisfies a second condition, including: the first update time is a time after the second update time;

The first data does not satisfy a second condition, comprising: the first update time is a time before the second update time;

the determining whether the first data satisfies a second condition further includes:

Determining whether the user data corresponds to a failure tag;

correspondingly, the first data meets the second condition, and further comprises: the user data does not correspond to an invalidation tag;

the first data does not satisfy the second condition, further comprising: the user data corresponds to a failure tag.

2. The method of claim 1, wherein the obtaining second data from the business system based on the query targeting information, determining a query result based on the first data and the second data, comprises:

Determining a first service system according to the query target information;

sending a second query request to the first service system through a real-time interface, wherein the second query request is used for requesting the first service system to feed back the latest data of the target user;

receiving second data sent by the first service system, wherein the second data comprises the latest data of a target user;

And determining a query result according to the first data and the second data.

3. The method according to claim 2, wherein the method further comprises:

if second data fed back by the first service system are received, determining a first update request according to the second data;

and sending a first updating request to the cache cluster, wherein the first updating request is used for requesting the cache cluster to update the user data corresponding to the target user.

4. The method according to claim 1, wherein the method further comprises:

Receiving data change information sent by a second service system, wherein the data change information comprises: user change data and/or business change data;

according to a preset service processing rule, determining the change data of the first type of service and/or the change data of the first type of user in the data change information;

If the data change information comprises change data of a first type of service, updating product asset information corresponding to the service in the cache cluster according to the change data of the first type of service;

If the data change information comprises change data of a first type of users, a first invalidation instruction is sent to the cache cluster, asynchronous refreshing is carried out according to the user identification of the first type of users and the change data of the first type of users, and an asynchronous refreshing result is obtained; updating personal asset information corresponding to a user in the cache cluster according to the asynchronous refreshing result, and deleting an invalidation tag; the first invalidation instruction is used for indicating the cache cluster to add invalidation labels to the user data.

5. The method of claim 4, wherein asynchronously refreshing based on the user identification of the first type of user and the change data of the first type of user to obtain an asynchronous refresh result comprises:

Determining a service type and at least one third service system corresponding to the change data according to the change data of the first type of users;

Sending a second updating request to each third service system according to the user identification of the first type of users so as to carry out asynchronous refreshing;

receiving an asynchronous refreshing result fed back by each third service system, and updating personal asset information corresponding to a user in the cache cluster according to the asynchronous refreshing result corresponding to each service type;

And/or the number of the groups of groups,

And receiving asset updating data sent by a fourth service system, and updating personal asset information corresponding to the user in the cache cluster according to the asset updating data.

6. The method according to any of claims 1 to 5, wherein the cache cluster comprises: a first cache set and a second cache set;

The first cache set includes product asset data for each of at least one business and an update timestamp for the product asset data;

the second cache set includes personal asset data for each of at least one user and an update timestamp for the personal asset data.

7. A service processing apparatus, the apparatus comprising:

The receiving module is used for receiving a first query request sent by the first terminal;

The first processing module is used for determining query target information according to the first query request and determining whether the query target information meets a first condition;

If the query target information meets a first condition, acquiring first data from a cache cluster according to the query target information; determining whether the first data meets a second condition, if the first data meets the second condition, determining a query result according to the first data, and if the first data does not meet the second condition, acquiring the second data from a service system according to the query target information, and determining the query result according to the first data and the second data;

If the query target information does not meet the first condition, third data are acquired from a service system according to the query target information, and a query result is determined according to the third data;

the sending module is used for sending the query result to the first terminal;

The first processing module is configured to determine query target information according to the first query request, where the query target information includes: target users and target services;

Determining whether the query target information meets a first condition according to a preset service processing rule, the target user and a target service;

correspondingly, the query target information meets a first condition, including:

Determining that a target user is a first type user and the target service is a first type service according to the preset service processing rule;

the query target information does not satisfy a first condition, including at least one of:

determining that the target service is a second type service according to the preset service processing rule;

determining that the target service is a first type service or a second type service according to the preset service processing rule, and the target user is a second type user;

the preset business processing rule is used for indicating at least one first type business and/or at least one first type user;

The first type of service is a service with a cache authority;

the first type of users are users with caching authority;

the second type of service is a service without caching authority;

The second class of users are users without caching rights;

wherein the first data includes: the first processing module is used for determining a first updating time corresponding to the user data;

Determining a second update time corresponding to the product data;

Determining a precedence relationship between the first update time and the second update time;

accordingly, the first data satisfies a second condition, including: the first update time is a time after the second update time;

The first data does not satisfy a second condition, comprising: the first update time is a time before the second update time;

The first processing module is further configured to:

Determining whether the user data corresponds to a failure tag;

correspondingly, the first data meets the second condition, and further comprises: the user data does not correspond to an invalidation tag;

the first data does not satisfy the second condition, further comprising: the user data corresponds to a failure tag.