CN113645304A

CN113645304A - Data service processing method and related equipment

Info

Publication number: CN113645304A
Application number: CN202110929195.8A
Authority: CN
Inventors: 马进朝; 董攀峰; 乔志奇; 张嘉佳; 王宵波; 杨宇
Original assignee: Hundsun Technologies Inc
Current assignee: Hundsun Technologies Inc
Priority date: 2021-08-13
Filing date: 2021-08-13
Publication date: 2021-11-12
Anticipated expiration: 2041-08-13
Also published as: CN113645304B

Abstract

The application provides a data service processing method and related equipment, which are used for predetermining whether various services support fragments, configuring one or more fragment clusters corresponding to the fragments if the fragments are supported, determining a database corresponding to each partition cluster, defining service information and the like related to user accounts which can be stored in the database, namely predetermining service configuration rules of various services. Therefore, after receiving a service calling request aiming at a target service sent by any user client, the access gateway equipment determines which service cluster corresponding to the target service the service calling request should be forwarded to according to a service configuration rule determined on an application layer in advance, responds to the service calling request, and calls required service information from a database connected with the access gateway equipment to feed the service information back to the user client, so that the service requirement of the user client is met.

Description

Data service processing method and related equipment

Technical Field

The present application relates to the field of micro service system applications, and more particularly, to a data service processing method and related device.

Background

The micro-service architecture is a new technology for deploying applications and services in the cloud, and users such as enterprises and service providers generally deploy distributed systems based on the micro-service architecture, so that different business data processing requirements of corresponding industries are met. Taking the financial industry as an example, the classified storage of various data such as various order transactions of different users can be realized, so that the corresponding database can be accessed later, the required business data can be inquired, and the like.

With the rapid increase of the user quantity, the expansion of the business and the transaction quantity is realized by adopting a database-based sub-table mode based on an agent/non-agent. In the non-proxy mode, a lib library is responsible for functions such as SQL (Structured Query Language) analysis, routing calculation and the like on a driving layer so as to realize sub-library and sub-table, and the realization difficulty is high, the process is complex, the SQL syntax limitation is adopted, and the cross-library data Query cannot be realized; the proxy mode is that the added proxy servers perform routing calculation according to configured fragment routing rules, the process is complex, the proxy servers are required to execute multiple network interactions, the system performance and the processing efficiency are reduced, and cross-library query cannot be performed due to SQL syntax limitation.

Therefore, how to simply and flexibly realize the capacity expansion of the distributed system without being restricted by the type of the database and meet the expansion requirements of the customer volume and the transaction volume becomes one of the problems to be solved urgently in the field.

Disclosure of Invention

In view of the above, in order to solve the above technical problem, the present application proposes the following technical solutions:

in one aspect, the present application provides a data service processing method, where the method includes:

receiving a service calling request sent by a user client;

analyzing the service calling request to obtain calling request information of the user client; the calling request information comprises a target service identifier of a target service requested to be called and fragmentation indication information aiming at the target service;

acquiring a target fragment cluster mapped by the target service identifier and the fragment indication information according to a service configuration rule corresponding to the target service identifier and constructed on an application layer;

and forwarding the service calling request to the target fragment cluster, so that the target fragment cluster responds to the service calling request, and calling the requested service information from a target database corresponding to the target fragment cluster and feeding the service information back to the user client.

Optionally, the obtaining, according to a service configuration rule corresponding to the target service identifier, a target fragment cluster mapped by the target service identifier and the fragment indication information includes:

calling a service configuration rule corresponding to the target service identifier;

determining whether the target service is configured with a plurality of fragment clusters according to the service configuration rule; the service information stored in the databases of the fragment clusters is different;

if yes, inquiring the fragment cluster mapped by the fragment indication information as a target fragment cluster according to the service configuration rule;

if not, forwarding the service calling request to a target cluster corresponding to the target service, so that the target cluster responds to the service calling request, and calling the requested service information from a target database corresponding to the target cluster and feeding the service information back to the user client.

Optionally, the querying, according to the service configuration rule, the segment cluster mapped by the segment indication information as a target segment cluster includes:

detecting whether the fragment indication information has a specified fragment identifier;

and if the designated fragment identifier exists, determining the designated fragment cluster corresponding to the designated fragment identifier as a target fragment cluster.

Optionally, the querying, according to the service configuration rule, the segment cluster mapped by the segment indication information as a target segment cluster further includes:

if the designated fragment identification does not exist, detecting whether a target user identification of the user client exists in the fragment indication information or not;

if the target user identification exists, inquiring the fragment cluster mapped by the target user identification as a target fragment cluster;

and if the target user identification does not exist, randomly selecting a fragmentation cluster as a target fragmentation cluster from the plurality of fragmentation clusters.

if the fragment cluster mapped by the target user identifier is not inquired, detecting whether a default fragment cluster exists in the plurality of fragment clusters;

and if so, determining the default fragment cluster as a target fragment cluster.

Optionally, the method further includes:

and if the designated fragment cluster corresponding to the designated fragment identifier does not exist or the default fragment cluster does not exist, outputting request forwarding exception prompt information.

Optionally, the target shard cluster responds to the service invocation request, and invokes the requested service information from a target database corresponding to the target shard cluster and feeds the service information back to the user client, including:

and the target fragment cluster calls a service process of the target fragment cluster according to a load balancing strategy so as to call service information requested by the user client in a target database corresponding to the target fragment cluster through the service process and feed the service information back to the user client.

Optionally, the building process of the service configuration rule includes:

acquiring service registration information of any type of service; the service registration information comprises a fragment field identifier for representing whether the service supports the fragment; if the service support fragment, aiming at the fragment identification of one or more fragment clusters constructed by the service and the user identification associated with the database corresponding to each fragment cluster, wherein the database is used for storing the service information corresponding to the associated user identification;

and constructing a service configuration rule corresponding to the service identifier of the service according to the service registration information.

In another aspect, the present application further provides a data service processing apparatus, including:

the service calling request receiving module is used for receiving a service calling request sent by a user client;

a calling request information obtaining module for analyzing the service calling request to obtain the calling request information of the user client; the calling request information comprises a target service identifier of a target service requested to be called and fragmentation indication information aiming at the target service;

a target fragment cluster obtaining module, configured to obtain a target fragment cluster mapped by the target service identifier and the fragment indication information according to a service configuration rule corresponding to the target service identifier and constructed on an application layer;

and the service calling request forwarding module is used for forwarding the service calling request to the target fragment cluster so that the target fragment cluster responds to the service calling request, and the requested service information is called from a target database corresponding to the target fragment cluster and fed back to the user client.

In yet another aspect, the present application further proposes an access gateway device comprising at least one memory and at least one processor, wherein:

the memory is used for storing programs for realizing the data service processing method;

the processor is used for calling and executing the program stored in the memory so as to realize the data service processing method.

In another aspect, the present application further provides a data service processing system, including:

a plurality of terminals;

the access gateway device is in communication connection with the terminal;

a plurality of service clusters, the service clusters communicatively connected with the access gateway device;

and the databases are connected with the service clusters in a one-to-one correspondence manner and are used for storing service information of corresponding types of services corresponding to different user identifications.

In yet another aspect, the present application also proposes a computer-readable storage medium, on which a computer program is stored, the computer program being called and executed by a processor, implementing the data service processing method as described above.

Therefore, the application provides a data service processing method and related equipment, and the application provides a fragmentation solution system elastic expansion on an application level, namely, whether the corresponding type of service supports the fragmentation is determined according to actual requirements aiming at various services of the industry in advance, if the fragmentation is supported, one or more corresponding fragmentation clusters are configured in advance, a database corresponding to each partitioning cluster is determined, service information and the like related to user accounts which can be stored in the database are defined, and the service configuration rule of each type of service is determined in advance. In practical application, any user client sends a service call request for a target service to the access gateway device, and the access gateway device in the application layer determines which service cluster the service call request should be forwarded to, or even determines which application process of the service cluster should forward the service call request to the access gateway device according to a service configuration rule obtained in advance, so that required service information is called from a database connected with the service cluster, and service requirements of the corresponding user client are met.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.

FIG. 1 is a schematic block diagram of an alternative example of a data service processing system as set forth in the present application;

fig. 2 is a schematic flow chart of an alternative example of the data service processing method proposed in the present application;

fig. 3 is a schematic flow chart of yet another alternative example of the data service processing method proposed in the present application;

fig. 4 is a schematic flow chart of yet another alternative example of the data service processing method proposed in the present application;

fig. 5 is a schematic hardware structure diagram of an alternative example of the data service processing apparatus proposed in the present application;

fig. 6 is a schematic structural diagram of an alternative example of an access gateway device suitable for the data service processing method proposed in the present application.

Detailed Description

The data service processing method aims at describing database sub-tables in the background technology part, and provides a method for processing database fragments on an application program level, replacing the above described database sub-table mode of the database level through service cluster expansion, and expanding a database and services as a whole, so that the technical problems of loss caused by multiple network interactions, SQL (Structured Query Language) statement constraint, complex routing calculation, no support of cross-database Query and the like of the independent database sub-table processing mode are solved, infinite expansion and capacity expansion of the whole distributed system are realized, and the application requirements caused by rapid increase of user quantity and transaction quantity in the financial industry are met. The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, 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 invention.

Referring to fig. 1, a schematic diagram of an alternative example of a data service processing system proposed in the present application may include: terminal 100, access gateway device 200, access server 300 and database 400, wherein:

electronic devices that can be used by the terminal 100, including but not limited to smart phones, tablet computers, personal computers, smart wearable devices, vehicle-mounted devices, robots, desktop computers, and the like, can be determined according to the requirements of the scene, and the application does not limit the type and data of the terminal 100.

In this embodiment of the present application, the terminal 100 may be installed with a client for a user to initiate a corresponding service request, may be an application installed independently, and may be a web application. For example, in the financial industry, the client may be a mobile banking machine, various financial management software, or an application with a financial management function, and the user may start the client, log in a registered application account, query a business owned by the client, query various data under the application account, execute some order transactions, and the like. It is understood that service functions supported by different types of clients may be different, and embodiments of the present application are not listed here.

The Access Gateway (AG) device 200 may be an edge Access layer located in a soft switch architecture, a unified Access point providing services to the outside, and a computer system or a device providing data conversion services between different networks, that is, a connector between different networks. In the three-layer IP Network, the Access gateway device generally refers to various IP gateway devices whose Network edge is connected to the user host, such as a Broadband Access gateway (BRAS), a wireless Access gateway (WiFi router), a home (Access) gateway, various dial-up (protocol) Access gateways, a Private Access gateway, a VPN (Virtual Private Network) Access gateway, an enterprise Access gateway, and the like.

In this embodiment, for a client on the terminal 100 used by a user, initiating a service invocation request, such as a data query request for querying account information, the client may send the service invocation request to the access gateway device 200, and the access gateway device 200 forwards the service invocation request to a corresponding database to query the account information stored in the database. It can be understood that the data transmission format of the service invocation request follows the communication protocol of the access gateway device 200, and the reliability of data transmission is ensured, and the implementation process of sending the service invocation request to the access gateway device 200 by the client is not described in detail in the present application.

The access server 300 may be a process server, and is configured to forward the service invocation request received by the access gateway device 200 to a corresponding database, so as to support the fragmentation in the service mode of implementing the distributed system. As shown in fig. 1, the present application may configure one service cluster for each database, that is, a service cluster composed of a plurality of access servers 300, and may provide a group of services composed of a plurality of application processes that are peer-to-peer and can replace the services with each other. One class of service may correspond to a plurality of service clusters, and each class of service may also correspond to one service cluster.

In the embodiment of the present application, whether to perform fragmentation processing on a corresponding type of service, that is, whether to configure routing fragmentation information (i.e., service configuration rule) that whether the type of service supports fragmentation forwarding processing, may be determined according to actual application requirements, for example, by determining whether a single machine can provide a required service, and by using this fragmentation processing manner, the service can be extended according to the amount of service information that needs to be provided. Therefore, under the condition that it is determined that a certain type of service supports shards, one or more shard clusters (i.e., service clusters) may be constructed for the type of service, and a database may be configured for each shard cluster to store service information of the type of service that some users have, so as to subsequently query service information required by each user according to a mapping relationship among the service type, the shard cluster, and the user identifier.

For example, referring to the system architecture shown in fig. 1, taking three services, namely service a, service B, and service C, provided by the system as an example for explanation, if service a and service B need to be fragmented, service C does not need to be fragmented, and multiple fragments (i.e. multiple service clusters) may be constructed for service a, including but not limited to fragment 1, fragment 2, and fragment 3 of service a shown in fig. 1, and these three fragments may be connected to different databases, and these three different databases may be used to store different data, such as account information of different accounts, and then during registering service a, these routing fragment information may be reported as part of service registration information and sent to access gateway device 200 for access gateway device 200 to thereby construct a service configuration rule of service a, that is, routing fragment information for service a, so that after subsequently receiving the service call request for the service a, the service call request can be forwarded to the corresponding fragment cluster response according to the routing fragment information.

Similarly, a fragment cluster may be constructed for service B, but is not limited to, as shown in service B fragment 1 in fig. 1, so that when registering service B, service B may be sent to access gateway apparatus 200 for storage with the corresponding routing fragment information. It can be understood that, for the service a and the service B supporting fragmentation, in the subsequent application, fragmentation expansion can be performed according to the expansion requirement without changing the original system architecture, which is very convenient, and the implementation method of fragmentation is not limited by the present application.

For the service C that does not support fragmentation, each access server supporting the service C connects to the same database, and is used to store the same type of data of the service C, and cannot expand the service C in subsequent applications. It should be noted that the present application does not limit the service types supported by the entire data service processing system and the number of fragmented clusters of each service, and can be adaptively adjusted according to actual needs, which is not described in detail herein.

As a result of the above analysis, in the process of registering each service that can be provided by the system, the routing fragment information may be sent to the access gateway device 200 to generate a service configuration rule for a corresponding type of service, for example, a fragment identifier of each fragment cluster of the type of service, a mapping relationship between account identifiers of different accounts (i.e., one user identifier, or user identifiers of other contents may also be used, which is not limited in this application) and different databases, and the content of the mapping relationship and the expression manner thereof are not limited in this application, which may be determined according to the circumstances.

For example, still taking the slicing service mode shown in fig. 1 as an example for description, the slicing database 1 of the service a slice 1 is used for storing account information of the account 1, that is, the account 1 corresponds to the service a slice 1; the fragment database 2 of the service a fragment 2 is configured to store account information of the account 2, that is, the account 2 corresponding to the service a fragment 2, and in practical application, the routing fragment information may be determined in an enumeration manner, an interval range manner, a fuzzy matching manner, and the like, which is not limited in this application.

The database 400 may be a data storage device, such as a database server, for storing data, and the type and composition of the database are not limited in this application and may be determined as appropriate. In combination with the fragmentation service described above, that is, after fragmentation is implemented on an application level, according to a fragmentation result, a database is configured for each fragmentation cluster to store service information of one or more accounts allocated to the fragmentation cluster, where data transmission can be implemented between the fragmentation cluster and the database by invoking multiple processes, and the data transmission method is not limited in this application.

Based on the description of each component of the system, after a user sends a service invocation request for a certain type of service through a client, the service invocation request is transmitted to the access gateway device 200, the access gateway device 200 parses a target service identifier of a target service invoked by the client request, and then, a service configuration rule (such as the routing fragment information) obtained during registration of the type of service can be obtained, a target fragment cluster corresponding to the service invocation request is determined according to the service invocation request, the service invocation request is forwarded to the target fragment cluster, the target fragment cluster responds to the service invocation request, and the required service information is retrieved from a target database connected with the target fragment cluster through an application process and fed back to the user client.

It can be seen that, the number of the databases 400 in the present application is multiple, each service cluster is correspondingly configured with one database for storing service information supporting or allocated or associated with each account having a service type corresponding to the cluster, each service type may correspond to at least one service cluster, and configuration information such as types of databases corresponding to different service clusters, storage spaces, and the like may be different, which is optional and not limited in the present application.

Based on the analysis, the data service processing system provided by the embodiment of the application directly realizes service fragment expansion on an application layer, not only simplifies the routing fragment processing, but also is beneficial to simplifying the subsequent data service processing method steps, reduces the data service processing difficulty, is not limited by SQL language any more, supports data query of various databases, and can realize cross-database query; and data are not required to be acquired from the proxy server through network interaction, so that the loss of the network interaction on the system performance is avoided, and the data service processing efficiency is improved.

Based on the composition structure of the data service processing system described in the foregoing embodiment, how to implement the process of the data service processing method in practical application will be described below, it should be noted that the process of the data service processing method implemented by the system includes, but is not limited to, the description content of the following embodiment, and in a case of no conflict, the embodiments and features in the embodiments in the present application may be combined with each other, and the present application is not described in detail by way of example.

Referring to fig. 2, a flowchart of an alternative example of the data service processing method proposed in the present application is illustrated, where the method may be executed by an access gateway device 200, and the product type of the access gateway device 200 may be determined as the case may be, and the present application is not limited by the embodiment. As shown in fig. 2, the method may include:

step S21, receiving a service calling request sent by a user client;

with reference to the description of the corresponding part of the above embodiment, in a process that any user uses a client in an electronic device, the user may access any type of service that the client can provide, and after the user determines a service to be accessed, the client generally needs to invoke service information that supports implementation of the service function in order to provide the service.

In practical application, the service invocation request sent by the user client may generally include information such as an account id of the user client, a target service id of a target service requested to be accessed, whether the requested access service requires fragmentation, and the like.

The account identifier may be an account address, a nickname, a user name, or other unique identity identifier of a registered account of a corresponding user on an application platform of the client; the service identifier can be used for distinguishing different types of services, representing the service types of corresponding services and the like, and can be a service type name, a preset number and the like.

Step S22, analyzing the service calling request to obtain the calling request information of the user client;

following the above description of the service invocation request, the invocation request information obtained by the access gateway device through parsing may include a target service identifier of a target service requested to be invoked, and fragment indication information for the target service, where the fragment indication information may indicate one or more fragment clusters corresponding to the target service among a plurality of fragment clusters corresponding to different preset types of services, and the content of the fragment indication information is not limited in the present application, and may be the preset fragment information indicating whether the target service is fragmented or not, and the like. The content included in the call request information is not limited, and can be determined according to the situation.

Step S23, according to the service configuration rule constructed on the application layer and corresponding to the target service identification, obtaining the target fragment cluster mapped by the target service identification and the fragment indication information;

in combination with the above description related to the system embodiment, the service configuration rules corresponding to the different types of services are generated in advance according to the fragmentation requirements of the different types of services, that is, whether the different types of services need to be fragmented or not is determined in advance, which database each fragmentation cluster corresponds to, and the database stores the service information of the type of service corresponding to which account number, and the like.

Based on this, after determining the target service requested to be invoked by any user client, the embodiment of the present application may determine, from service configuration rules corresponding to different types of services configured in advance, a service configuration rule corresponding to the target service, that is, a service configuration rule corresponding to a target service identifier indicating the target service, and then may obtain, according to the determined service configuration rule, a target fragment cluster to which the target service identifier and the fragment indication information are mapped. Therefore, the service configuration rule can represent that several fragment clusters are configured during the registration of the type of service, each distribution cluster corresponds to which application processes, and service information of which accounts stored in which database can be acquired through each application process, and the like.

For example, still as described by taking the fragmented service mode shown in fig. 1 as an example, the target service may be the service a in fig. 1, because the service a is configured with three fragmented clusters in advance, each distribution cluster may access a corresponding database through multiple application processes to call service information of the target service owned by a corresponding account, and for the fragmented service mode of the service a, the present application may determine which application process of which fragment the account of different users corresponds to during registration of the service a, store the service information of the service a associated with the account into the database corresponding to the application process, that is, determine in advance a service configuration rule for the service a, that is, a correspondence between the account identification of different users and each application process in different fragmented clusters, and each fragmented cluster corresponds to one database, to store service information of the corresponding user.

Based on this, after it is determined that the user client calls the service a, the fragment cluster corresponding to the account id of the user client may be determined as the target fragment cluster according to the predetermined service configuration rule, and the database corresponding to the target fragment cluster is determined as the target database.

Certainly, in some application scenarios, a user may also designate a segment cluster for responding to a service invocation request for the service a sent by its client, so that the access gateway device may determine the designated segment cluster carried by the service invocation request as a target segment cluster.

In still other embodiments, if the determined service configuration rule does not predetermine the segment cluster corresponding to a certain user, the present application may also determine a preset default segment cluster, a target segment cluster for transmitting the service invocation request sent by the user client, and the like. Therefore, under different application scenarios, the implementation manners of determining the fragment clusters corresponding to each user client having any type of service may be different, and therefore, the service configuration rule corresponding to the type of service may include, but is not limited to, the above-described correspondence, default configuration rule, specified rule, and the like, and may be determined according to actual requirements.

As described above, the service configuration rule for any type of service may be constructed during service registration and sent to the access gateway device for storage, so that after receiving a service invocation request sent by a user client, the access gateway device may determine, according to the stored service configuration rule for each service type, to which segment cluster the service invocation request is sent, and invoke, by which application process of the segment cluster, service information corresponding to the user account stored in the corresponding database.

In addition, as shown in fig. 1, for different types of services, unlike the above-described fragmentation configuration of the service a, there may be a fragmentation configuration in which there is one distribution cluster, such as the service B, or there may be a non-fragmentation configuration, such as the service C. Therefore, when the access gateway device determines that the target service included in the access gateway device belongs to service B or service C by analyzing the service invocation request, according to the corresponding service configuration rule, it may determine that one fragment cluster currently configured by service B is the target fragment cluster, and if a subsequent fragment expansion is continued for service B according to the scene requirement, so that after a plurality of fragment clusters are corresponding to the fragment cluster, the service configuration rule of service B may be updated correspondingly, and the invocation of the service information of service B is realized by referring to the upper invocation process of the service information of service a, which is not described herein again in this embodiment.

For the service C shown in fig. 1, because the service C cannot be fragmented, after receiving a service invocation request for the service C, the access gateway device directly sends the service invocation request to the service cluster of the service C, so as to invoke the required service information from the database.

In summary, the application utilizes a pre-established service configuration rule, and the application layer support is adopted to realize the cluster positioning function, and particularly, under the condition of calling the service support fragment requested, the access gateway device can utilize the fragment indication information such as the account identification of the user client to determine the target fragment cluster for forwarding the service calling request and calling the required service information from the corresponding database, thereby simplifying the data service processing steps, improving the processing efficiency, supporting the cross-database data query, better meeting the service requirements and improving the user experience.

It should be understood that, for the target shard cluster determined in the present application, one or more shard clusters in the multiple shard clusters corresponding to the target service may be used, so that the service information of the same user account may be stored in one or more databases, thereby implementing cross-repository data query.

Step S24, forwarding the service invocation request to the target fragment cluster, so that the target fragment cluster responds to the service invocation request, and invokes the requested service information from the target database corresponding to the target fragment cluster and feeds the service information back to the user client.

For a service invocation request sent by any user client for a certain service, after determining a target fragment cluster responding to the service invocation request according to the manner described above, the access gateway device may forward the service invocation request to the target fragment cluster, so that the target fragment cluster responds to the service invocation request, query, by an application process, service information corresponding to a user account of the user client in a target database corresponding to the target fragment cluster, and feed the queried service information back to the user client, so as to meet the service requirement of the user client.

As described above, in the face of the user amount and the order transaction amount which are rapidly increased in the financial industry, the application proposes the flexible expansion of the fragmentation solution system on the application level, that is, it is determined whether the corresponding type of service supports the fragmentation in combination with the actual requirements for each type of service in advance, if the fragmentation is supported, one or more corresponding fragmentation clusters are configured in advance, a database corresponding to each fragmentation cluster is determined, service information and the like associated with which user account numbers can be stored in the database are defined, that is, the service configuration rule of each type of service is determined in advance. In practical application, any user client sends a service call request for a target service to the access gateway device, and the access gateway device in the application layer determines which service cluster the service call request should be forwarded to, or even determines which application process of the service cluster should forward the service call request to the access gateway device according to a service configuration rule obtained in advance, so that required service information is called from a database connected with the service cluster, and service requirements of the corresponding user client are met.

Based on this, with the increase of the user quantity and/or the transaction quantity, the corresponding relationship between the corresponding user account and the fragment clusters of each type of service can be directly configured according to the method, and/or the service information generated by the order transaction of a certain service executed by each user is sent to the corresponding database for storage, so that the unlimited client quantity and transaction quantity expansion requirements of the financial service system are met.

Referring to fig. 3, a flow diagram of another optional example of the data service processing method proposed in the present application is shown, where this embodiment may be an optional detailed implementation method of the data service processing method described in the foregoing embodiment, but is not limited to this detailed implementation method, and the method may still be performed by the access service device, as shown in fig. 3, where the detailed implementation method may include:

step S31, receiving a service calling request sent by a user client;

step S32, analyzing the service calling request to obtain the calling request information of the user client;

the calling request information may include a target service identifier of a target service requested to be called, and fragmentation indication information for the target service, and the like.

Regarding the implementation process of step 31 and step S32, reference may be made to the description of the corresponding parts in the above embodiments, which is not described in detail in this embodiment.

Step S33, calling a service configuration rule which is constructed on the application layer and corresponds to the target service identification of the target service requested to be called;

step S34, according to the service configuration rule, determining whether the target service is configured with a plurality of fragment clusters, if yes, entering step S35; if not, go to step S37;

in combination with the description of the corresponding part of the above embodiment, different types of services may be configured with corresponding service identifiers, and a service configuration rule constructed for each type of service may characterize a mapping relationship between each user and one or more databases storing service information of the type of service, where the mapping relationship may be generated according to one or more service clusters configured for the type of service, and each service cluster may correspond to one database, and it is apparent that each database mapped by the type of service may be used to store service information of different users, that is, service information stored in databases connected to each of a plurality of shard clusters constructed on an application layer is different.

It should be noted that, the present application does not limit the content of the service configuration rule and the construction method thereof, and may be determined according to the circumstances, and for various services of the financial service, slices are not necessarily supported, as shown in fig. 1, some types of services may support slices, and one or more slice clusters are constructed at the application layer; some types of services do not support fragmentation, and an access server connected to a database storing service information of the type of services may be referred to as a service cluster.

Step S35, according to the service configuration rule, inquiring the fragment cluster mapped by the fragment indication information in the service calling request as a target fragment cluster;

step S36, the service calling request is sent to the target fragment cluster, so that the target fragment cluster responds to the service calling request, and the requested service information is called from the target database corresponding to the target fragment cluster and fed back to the user client;

in combination with the description of the corresponding part of the above embodiment, since the mapping relationship between different user clients (i.e. different user accounts) and different fragment clusters of the target service, or the mapping relationship between different user clients and different fragment databases has been clarified in the service configuration rule of the target service, the present application may query the fragment cluster mapped by the fragment indication information according to the service configuration rule after obtaining the fragment indication information from the service invocation request, such as the user account id, the designated fragment id, and so on, and use it as the target fragment cluster to respond to the service invocation request sent by the user client, invoke the required service information from the corresponding target database, and feed it back to the user client, thereby satisfying the corresponding service requirements.

It should be noted that, in the present application, there is no limitation on how each fragment cluster responds to the service invocation request, and an implementation process of invoking the service information required by the current user from the database connected to the fragment cluster is not limited. In some embodiments, the service configuration rule may specify service information of each user stored in the database, and the service information may be invoked through which application process of which shard cluster, so that in determining a target shard cluster, a target application process corresponding to the shard indication information in the target shard cluster may be further determined, so as to implement invocation of the service information through the target application process, but is not limited to this implementation manner.

Step S37, forwarding the service invocation request to the target cluster corresponding to the target service, so that the target cluster responds to the service invocation request, and invokes the requested service information from the target database corresponding to the target cluster and feeds the service information back to the user client.

As described above, the target service requested to be invoked by the user client does not support fragmentation, and the service information of the service of the type is stored in one database, in this case, the service cluster corresponding to the service of the type may be determined as the target cluster, and subsequently, the service information associated with the user account stored in the connected database may be invoked and fed back to the user client in the manner described above.

In summary, the embodiment of the application solves the problem of system elastic expansion by constructing corresponding fragment clusters for different types of applications on an application level, and meets the expansion requirements of unlimited client quantity and transaction quantity of corresponding service systems.

Referring to fig. 4, which is a flowchart illustrating a further optional example of the data service processing method proposed in the present application, this embodiment may be a further optional detailed implementation method of the data service processing method described in the foregoing embodiment, and this method may still be executed by an access gateway device, as shown in fig. 4, and this method may include:

step S41, receiving a service calling request sent by a user client;

step S42, parsing the service invocation request to obtain a target service identifier of a target service requested to be invoked by the user client and fragmentation indication information for the target service;

step S43, calling a service configuration rule which is constructed on an application layer and corresponds to the target service identification;

step S44, according to the service configuration rule, determining the respective fragment identification of a plurality of fragment clusters configured by the target service;

regarding the implementation process of step S41 to step S44, reference may be made to the description of the corresponding parts in the above embodiments, which is not repeated in this embodiment.

In some embodiments provided in the present application, the service configuration rule for each service may be constructed by the access gateway device according to service registration information when the service is registered, where the service registration information may include a fragment field identifier used to represent whether the service supports fragmentation; under the condition that the service supports the fragmentation, aiming at the respective fragmentation identifications of one or more fragmentation clusters constructed by the service and the user identifications associated with the databases corresponding to the fragmentation clusters, the databases are used for storing the service information corresponding to the associated user identifications.

Therefore, the access gateway device of the present application may construct a service configuration rule corresponding to the service identifier of the service according to the service registration information described above, so that, in practical applications, after determining the target service identifier of the target service, the service configuration rule corresponding to the target service identifier may be directly called from the service configuration rules corresponding to each service identifier, so as to know whether the target service supports fragmentation, that is, whether multiple fragmentation clusters are configured, specifically, the access gateway device may determine according to the content of the fragmentation field identifier included in the service configuration rule, that is, the fragmentation field identifier is the first content, which may indicate that the target service does not support fragmentation, and if the fragmentation field identifier is the second content, which may indicate that the target service supports fragmentation, the first content and the second content may be 1 and 0, respectively, but are not limited thereto.

In this way, by detecting the fragment field identifier content included in the service configuration rule corresponding to the target service identifier, determining whether the target service supports fragments, and if so, obtaining the respective fragment flag of one or more fragment clusters configured for the target service.

Step S45, detecting whether the designated fragment mark exists in the fragment indication information, if not, entering step S46; if yes, go to step S411;

in practical application, in some application scenarios, if a user knows different service information respectively stored in databases connected to different sharded clusters, one or more sharded clusters may be directly specified, and the required service information may be directly called from the database connected to the sharded clusters.

It should be noted that, an implementation manner in which a user client designates one or more segment clusters and retrieves required service information from a database connected to the segment clusters is not limited to the above-described online designation implementation manner, that is, when a service invocation request is initiated, the segment clusters may also be designated by a user and registered in advance to be determined and notified to the access gateway device.

Based on the above analysis, after receiving a service invocation request sent by a user client, the access gateway device in the embodiment of the present application may detect whether the service invocation request includes an assigned fragment identifier, that is, whether the assigned fragment identifier exists in the fragment indication information carried in the service invocation request, if the assigned fragment identifier exists, that is, the user specifies a fragment cluster for obtaining service information, the directly specified fragment cluster may be determined as a target fragment cluster, and the service information of the user is invoked from a corresponding database.

Step S46, detecting whether the piece indication information has a target user identification, if yes, entering step S47; if not, go to step S413;

step S47, detecting whether a target user identifier exists in the user identifiers corresponding to the plurality of fragment identifiers, and if so, entering step S48; if not, go to step S49;

step S48, determining the target user mark mapped slice cluster as target slice cluster;

as described above, if the user initiates a service invocation request, and does not specify a fragment cluster responding to the service invocation request, it may further detect whether the service invocation request includes a user identifier for indicating the user, such as information of an account name, an address, and the like of an application platform where the user is registered on the client, and if the user client provides the user identifier of the user, the access gateway device may detect whether a corresponding fragment cluster is configured for the user according to each service configuration rule acquired in advance, that is, whether a target user identifier of the user client exists in user identifiers corresponding to a plurality of fragment clusters of the service, and if so, it indicates that the fragment cluster is allocated to the user in advance; otherwise, it means that the user is not assigned a shard cluster in advance, and it is necessary to further determine the shard cluster responding to the service invocation request sent by the user client.

As can be seen, in the embodiment of the present application, when it is determined that the service invocation request includes the target user identifier, the target user identifier may be used as an input parameter, the corresponding service configuration rule is input to obtain the corresponding fragment identifier, and the fragment cluster having the fragment identifier is determined as the target fragment cluster.

If the information content carried by the service invocation request is analyzed, it is determined that the information content does not contain the target user identifier of the user client, as described below, one fragment cluster can be randomly selected as a target fragment cluster to respond to the service invocation request aiming at the target service sent by the user client; of course, a target shard cluster can be selected according to the load condition of each shard cluster, and the method for determining the target shard cluster in such a scenario is not limited by the application and can be determined according to the situation.

Step S49, detecting whether a default fragment cluster exists in the plurality of clusters, if yes, entering step S410; if not, go to step S414;

step S410, determining a default fragment cluster as a target fragment cluster;

according to the detection method described above, although the user client provides its target user identifier, in the service registration stage, the corresponding fragment cluster is not allocated to the target user identifier, and the access gateway device cannot query the target user identifier for the user identifiers corresponding to the fragment identifiers, in this case, a preset default fragment cluster can be selected as the target fragment cluster responding to the service invocation request, if the default fragment cluster is not set in advance, the request forwarding exception prompt information can be output, so that the user can accordingly re-initiate the service invocation request not including the target user identifier, or the service invocation request including the specified fragment identifier, or the fragment identifier corresponding to the request registration target user identifier, and after receiving the successful registration feedback information, re-send the service invocation request, etc., the application does not limit the subsequent processing method of requesting to forward exception prompt information, as the case may be.

Step S411, whether an appointed fragment cluster corresponding to the appointed fragment identification exists or not is judged, and if yes, the step S412 is executed; if not, go to step S414;

step S412, determining the designated fragment cluster as a target fragment cluster;

step S413, randomly selecting a shard cluster from the plurality of shard clusters as a target shard cluster;

step S414, outputting request forwarding exception prompt information;

as described above, when a user initiates a service invocation request through a client, a designated fragment identifier is provided, but the designated fragment identifier does not really exist, that is, the designated fragment identifier may not exist in the fragment identifiers of the plurality of fragment clusters corresponding to the target service, which means that the operation of the user-designated fragment cluster in response to the service invocation request is not successful, and in this case, request forwarding exception notification information may be output in the manner described above to remind the user to re-initiate the service invocation request; and a fragmentation cluster can also be randomly selected as a target fragmentation cluster, and the like, which is not limited in the present application.

Step S415, the service invocation request is sent to the target shard cluster, and the target shard cluster invokes the requested service information from the target database through the corresponding application process according to the load balancing policy, and feeds the service information back to the user client.

In practical application, the present application does not limit the implementation process of any service cluster (such as the above target shard cluster) in response to a received service invocation request sent by each user client according to a load balancing policy, for example, multiple application processes of the service cluster may be distributed in turn, or may be distributed according to a preset proportional weight, and the like, which may be determined as the case may be, and the embodiments of the present application are not described in detail herein.

To sum up, in the embodiment of the present application, by fragmenting different types of services on an application layer, and replacing the database and table partitioning of a database layer with different fragmentation clusters, the database and the services are extended as a whole (i.e., a service cluster), thereby solving the technical problems of performance loss caused by network interaction, incapability of realizing cross-database query due to SQL language constraint, complex routing, reduced processing efficiency, and the like in the database table partitioning method, that is, the present application can simply and flexibly realize unlimited extension and capacity expansion of the system without being constrained by the database types, and meet the application requirements of unlimited client volume and transaction volume expansion of financial services.

Referring to fig. 5, a schematic structural diagram of an alternative example of the data service processing apparatus proposed in the present application may include:

a service call request receiving module 51, configured to receive a service call request sent by a user client;

a calling request information obtaining module 52, configured to analyze the service calling request to obtain calling request information of the user client; the calling request information comprises a target service identifier of a target service requested to be called and fragmentation indication information aiming at the target service;

a target fragment cluster obtaining module 53, configured to obtain a target fragment cluster mapped by the target service identifier and the fragment indication information according to a service configuration rule corresponding to the target service identifier and constructed on an application layer;

a service invocation request forwarding module 54, configured to forward the service invocation request to the target fragment cluster, so that the target fragment cluster responds to the service invocation request, and invokes the requested service information from a target database corresponding to the target fragment cluster and feeds the service information back to the user client.

Optionally, the target shard cluster may include:

and the response unit is used for calling the service process of the target fragment cluster according to the load balancing strategy so as to call the service information requested by the user client in the target database corresponding to the target fragment cluster through the service process and feed the service information back to the user client.

In some embodiments proposed in the present application, the target shard cluster obtaining module 53 may include:

the service configuration rule calling unit is used for calling a service configuration rule corresponding to the target service identifier;

the fragment configuration detection unit is used for determining whether the target service is configured with a plurality of fragment clusters according to the service configuration rule; the service information stored in the databases of the fragment clusters is different;

a target fragment cluster querying unit, configured to query, according to the service configuration rule, a fragment cluster mapped by the fragment indication information as a target fragment cluster if a detection result of the fragment configuration detecting unit is yes;

and the first service call request forwarding unit is used for forwarding the service call request to a target cluster corresponding to the target service under the condition that the detection result of the fragmentation configuration detection unit is negative, so that the target cluster responds to the service call request, and calls the requested service information from a target database corresponding to the target cluster and feeds the service information back to the user client.

In a possible implementation manner, the target shard cluster querying unit may include:

an appointed fragmentation mark detection unit for detecting whether the fragmentation indication information has an appointed fragmentation mark;

and the first target fragment cluster determining unit is used for determining the designated fragment cluster corresponding to the designated fragment identifier as the target fragment cluster under the condition that the detection result of the designated fragment identifier detecting unit is yes.

A target user identifier detection unit, configured to detect whether a target user identifier of the user client exists in the segment indication information or not, if a detection result of the designated segment identifier detection unit is negative;

the second target fragment cluster determining unit is used for inquiring the fragment cluster mapped by the target user identifier as a target fragment cluster under the condition that the detection result of the target user identifier detecting unit is yes;

and the third target fragmentation cluster determining unit is used for randomly selecting a fragmentation cluster as a target fragmentation cluster from the plurality of fragmentation clusters under the condition that the detection result of the target user identification detecting unit is negative.

Optionally, the second target shard cluster determining unit may include:

the first query unit is used for querying the fragment cluster mapped by the fragment indication information as a target fragment cluster;

a default fragmented cluster detection unit, configured to detect whether a default fragmented cluster exists in the multiple fragmented clusters when a fragmented cluster mapped by a target user identifier is not queried;

and the fourth target fragmented cluster determination unit is configured to determine the default fragmented cluster as the target fragmented cluster if the detection result of the default fragmented cluster detection unit is yes.

And the abnormity prompting module is used for outputting request forwarding abnormity prompting information under the condition that the detection result of the default fragment cluster detection unit is negative.

Based on the apparatus described in the foregoing embodiments, in order to construct the service configuration rule corresponding to each type of service, the apparatus may further include:

the service registration information acquisition module is used for acquiring service registration information of any type of service;

the service registration information may include a fragment field identifier used to characterize whether the service supports fragmentation; if fragmentation is supported, aiming at information such as respective fragmentation identifications of one or more fragmentation clusters constructed by the service, and user identifications associated with a database corresponding to each fragmentation cluster, the database can be used for storing service information corresponding to the associated user identifications;

and the service configuration rule building module is used for building a service configuration rule corresponding to the service identifier of the service according to the service registration information.

It should be noted that, various modules, units, and the like in the embodiments of the foregoing apparatuses may be stored in the memory as program modules, and the processor executes the program modules stored in the memory to implement corresponding functions, and for the functions implemented by the program modules and their combinations and the achieved technical effects, reference may be made to the description of corresponding parts in the embodiments of the foregoing methods, which is not described in detail in this embodiment.

The present application further provides a computer-readable storage medium, on which a computer program can be stored, which can be called and loaded by a processor to implement the steps of the data service processing method described in the above embodiments.

Referring to fig. 6, which is a schematic diagram illustrating a hardware structure of an alternative example of an access gateway device suitable for the data service processing method proposed in the present application, as shown in fig. 6, the access gateway device may include at least one memory 61 and at least one processor 62, where:

the memory 61 may be used to store a program for implementing the data service processing method described in the above-described method embodiments; the processor 62 may be configured to call and execute the program stored in the memory 61 to implement the steps of the data service processing method according to the corresponding method embodiment, and the specific implementation process may refer to the description of the corresponding embodiment above, which is not described herein again.

In the present embodiment, the memory 61 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device or other volatile solid-state storage device. The processor 62 may be a Central Processing Unit (CPU), an application-specific integrated circuit (ASIC), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic device.

In combination with the description of the above method embodiment, the memory 61 may also be configured to store service configuration rules corresponding to different types of services, such as routing fragment information, and in order to obtain relevant information for constructing the service configuration rules, the access gateway device may further include communication interfaces, such as data interfaces of communication modules, such as a WIFI module, a 5G/6G (fifth generation mobile communication network/sixth generation mobile communication network) module, and a GPRS module, for implementing communication connection with each service cluster, communication connection with different terminals, and the like.

It should be understood that, for different types of communication interfaces, the number interaction with the connected terminal/service cluster and other devices may be implemented according to the communication protocol followed by the corresponding communication mode, and the implementation process is not described in detail in this application.

In addition, the structure of the access gateway device shown in fig. 6 does not constitute a limitation to the access gateway device in the embodiment of the present application, and in practical applications, the access gateway device may include more or less components than those shown in fig. 6, or may combine some components, which is not listed here.

Finally, it should be noted that, in the embodiments, relational terms such as first, second and the like may be used solely to distinguish one operation, unit or module from another operation, unit or module without necessarily requiring or implying any actual such relationship or order between such units, operations or modules. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method or system that comprises the element.

The embodiments in the present description are described in a progressive or parallel manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device, the system and the equipment disclosed by the embodiment correspond to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.

The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for processing data services, the method comprising:

receiving a service calling request sent by a user client;

2. The method according to claim 1, wherein the obtaining a target fragment cluster mapped by the target service identifier and the fragment indication information according to a service configuration rule corresponding to the target service identifier comprises:

3. The method according to claim 2, wherein said querying the shard cluster mapped by the shard indication information as a target shard cluster according to the service configuration rule comprises:

4. The method according to claim 3, wherein said querying the shard cluster mapped by the shard indication information as a target shard cluster according to the service configuration rule further comprises:

5. The method according to claim 4, wherein said querying the shard cluster mapped by the shard indication information as a target shard cluster according to the service configuration rule further comprises:

6. The method according to any one of claims 3 to 5, further comprising:

7. The method according to any one of claims 1 to 5, wherein the retrieving, by the target shard cluster, the requested service information from a target database corresponding to the target shard cluster and feeding the service information back to the user client in response to the service invocation request includes:

8. The method according to any one of claims 1 to 5, wherein the construction process of the service configuration rule comprises:

9. A data service processing apparatus, characterized in that the apparatus comprises:

10. An access gateway device, comprising at least one memory and at least one processor, wherein:

the memory for storing a program for implementing the data service processing method according to any one of claims 1 to 8;

the processor is used for calling and executing the program stored in the memory so as to realize the data service processing method according to any one of claims 1 to 8.

11. A data service processing system, the system comprising:

a plurality of terminals;

the access gateway device of claim 10, the access gateway device communicatively coupled with the terminal;

12. A computer-readable storage medium, having stored thereon a computer program, which is invoked and executed by a processor, implementing a data service processing method according to any one of claims 1 to 8.