A data service processing method, device, computing device and storage medium

Abstract

The present disclosure is about a data service processing method, device, computing equipment and storage medium, which belongs to the field of computer technology and is used to provide strongly typed business data calls to improve business access efficiency. In this method, a call request initiated by a service user by calling a data service interface is received, wherein the data service interface is a pre-created strongly typed call interface, and the associated data corresponding to the data service interface is a strongly typed description method, and the call request includes target request parameters; in response to the call request, the target data corresponding to the target request parameters is determined from the associated data; and the target data is sent to the service user so that the service user performs business according to the target data. In this way, strongly typed data can be called directly, which enhances the data service capabilities of the data platform.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a data service processing method, device, computing equipment and storage medium. Background Art

[0002] At present, with the application and popularization of big data technology and cloud computing technology, many data platforms can provide business parties with data services based on big data. Specifically, the data platform is equipped with a processing program corresponding to the data service and provides users with a calling interface corresponding to the data service, wherein the calling interface corresponding to the data service is used to trigger the running of the processing program corresponding to the data service, and the calling interface is, for example, an application programming interface (Application Programming Interface, API).

[0003] The calling interfaces of existing data platforms that provide data services to business systems are all weakly typed interfaces, and the business data obtained by business systems through these calling interfaces are also described in a weakly typed manner. When using these data to process business, the business system needs to parse the weakly typed data and perform other specific processing before it can be used. This is inefficient in processing business and is prone to errors in the process of parsing data, making the basic data for executing business inaccurate, resulting in low effectiveness of business processing. Summary of the invention

[0004] The present disclosure provides a data service processing method, device, computing equipment and storage medium, which are used to provide strongly typed service data calls and improve service access efficiency.

[0005] The technical solution of the present disclosure is as follows:

[0006] In a first aspect, a method for processing a data service is provided, the method comprising:

[0007] Receiving a call request initiated by a service user by calling a data service interface, wherein the data service interface is a pre-created strongly typed call interface, the associated data corresponding to the data service interface is a strongly typed description method, and the call request includes a target request parameter;

[0008] In response to the call request, determining target data corresponding to the target request parameter from the associated data;

[0009] The target data is sent to the service user so that the service user executes the business according to the target data.

[0010] Optionally, the data service interface is created in the following manner:

[0011] Acquire interface creation information inputted into the interface creation interface, the interface creation information including a data source identifier and conversion parameter configuration information, the conversion parameter configuration information being used to indicate a target field corresponding to a request parameter and / or a return parameter to be converted;

[0012] Calling a strong type generation service to convert data corresponding to the target field in the source data indicated by the data source identifier into strongly typed data to obtain a data conversion result;

[0013] The data service interface is created according to the interface creation code and the data conversion result.

[0014] Optionally, the interface creation information further includes an interface query parameter threshold, and the method further includes:

[0015] Determining a target cache type according to the interface query parameter threshold;

[0016] Selecting a target storage unit whose cache type is the target cache type from the cache cluster;

[0017] The converted strongly typed data is stored in the target storage unit.

[0018] Optionally, selecting a target storage unit whose cache type is the target cache type from the cache cluster includes:

[0019] Determine candidate storage units whose cache types are the target cache type from the cache cluster, and select a storage unit whose storage capacity can store the strongly typed data from the candidate storage units as the target storage unit; or

[0020] If the capacity of an initial storage unit whose cache type is the target cache type determined in the cache cluster is insufficient to store the strongly typed data, the initial storage unit is expanded and the expanded initial storage unit is determined as the target storage unit.

[0021] Optionally, the interface creation information further includes interface importance level indication information. After creating the data service interface according to the interface creation code and the data conversion result, the method further includes:

[0022] Determining a corresponding target group from a plurality of interface groups according to the interface importance level indicated by the interface importance level indication information, wherein the interface importance levels of the respective interface groups are different;

[0023] The newly created data service interface is divided into the target group.

[0024] Optionally, responding to the call request includes:

[0025] Determining whether the calling frequency of the data service interface within a predetermined time period is less than a predetermined threshold;

[0026] If the calling frequency of the data service interface within the predetermined time period is less than the predetermined threshold, determining whether the priority of the calling request is higher than other requests waiting to be processed;

[0027] If the priority of the call request is higher than that of the other requests, the call request is processed, and the other requests are processed after the call request is processed.

[0028] Optionally, the call request also includes a user identifier, and responding to the call request includes:

[0029] Determine a call interface set that the user identifier has call permission for, and if the data service interface belongs to the call interface set, respond to the call request; or,

[0030] A set of users having calling authority for the data service interface is determined, and if the user identifier belongs to the set of users, the calling request is responded to.

[0031] In a second aspect, a data service processing device is provided, the device comprising:

[0032] A receiving unit is configured to execute a call request initiated by a monitoring service user by calling a data service interface, wherein the data service interface is a pre-created strongly typed call interface, the associated data corresponding to the data service interface is a strongly typed description method, and the call request includes a target request parameter;

[0033] A response unit, configured to execute a response to the call request and determine target data corresponding to the target request parameter from the associated data;

[0034] The sending unit is configured to send the target data to the service user so that the service user executes the service according to the target data.

[0035] Optionally, the device further includes a creating unit, wherein the creating unit is configured to execute:

[0036] Acquire interface creation information inputted into the interface creation interface, the interface creation information including a data source identifier and conversion parameter configuration information, the conversion parameter configuration information being used to indicate a target field corresponding to a request parameter and / or a return parameter to be converted;

[0037] Calling a strong type generation service to convert data corresponding to the target field in the source data indicated by the data source identifier into strongly typed data to obtain a data conversion result;

[0038] The data service interface is created according to the interface creation code and the data conversion result.

[0039] Optionally, the interface creation information further includes an interface query parameter threshold, and the device further includes a storage unit, and the storage unit is configured to execute:

[0040] Determining a target cache type according to the interface query parameter threshold;

[0041] Selecting a target storage unit whose cache type is the target cache type from the cache cluster;

[0042] The converted strongly typed data is stored in the target storage unit.

[0043] Optionally, the storage unit is configured to execute:

[0044] Determine candidate storage units whose cache types are the target cache type from the cache cluster, and select a storage unit whose storage capacity can store the strongly typed data from the candidate storage units as the target storage unit; or

[0045] If the capacity of an initial storage unit whose cache type is the target cache type determined in the cache cluster is insufficient to store the strongly typed data, the initial storage unit is expanded and the expanded initial storage unit is determined as the target storage unit.

[0046] Optionally, the interface creation information further includes interface importance level indication information, and the creation unit is configured to execute:

[0047] Determining a corresponding target group from a plurality of interface groups according to the interface importance level indicated by the interface importance level indication information, wherein the interface importance levels of the respective interface groups are different;

[0048] The newly created data service interface is divided into the target group.

[0049] Optionally, the response unit is configured to execute:

[0050] Determining whether the calling frequency of the data service interface within a predetermined time period is less than a predetermined threshold;

[0051] If the calling frequency of the data service interface within the predetermined time period is less than the predetermined threshold, determining whether the priority of the calling request is higher than other requests waiting to be processed;

[0052] If the priority of the call request is higher than that of the other requests, the call request is processed, and the other requests are processed after the call request is processed.

[0053] Optionally, the call request further includes a user identifier, and the response unit is configured to execute:

[0054] Determine a call interface set that the user identifier has call permission for, and if the data service interface belongs to the call interface set, respond to the call request; or,

[0055] A set of users having calling authority for the data service interface is determined, and if the user identifier belongs to the set of users, the calling request is responded to.

[0056] According to a third aspect, a computing device is provided, including:

[0057] A processor, and a memory for storing processor executable instructions; wherein the processor is configured to execute the instructions to implement the data service processing method of any one of the first aspects.

[0058] In a fourth aspect, a storage medium is provided. When instructions in the storage medium are executed by a processor of a computing device, the computing device is enabled to execute the data service processing method of any one of the first aspects.

[0059] In a fifth aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is enabled to execute the steps included in the method for processing data services described in the various possible implementations described above.

[0060] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:

[0061] A strongly typed data service interface can be pre-created in the data platform, that is, a strongly typed calling interface can be created, and the data associated with the strongly typed calling interface is also described in a strongly typed manner. In this way, when the service user (such as a business system) calls such a data service interface to request data from the data platform, it can obtain strongly typed return data. In other words, the data platform can directly provide strongly typed return data based on the service user's calling request. In this way, the service user can use the strongly typed business data directly after obtaining it, without the need for further parsing and other processing. This can avoid data errors as much as possible, improve the effectiveness of business processing, and also save processing time and improve business processing efficiency.

[0062] Based on the technical solution in the embodiments of the present disclosure, the data platform can dynamically create a strongly typed data service interface. Based on the created strongly typed data service interface, it can provide strongly typed data calls. On the basis of traditional calls that support weakly typed data, new types of called data are added, enriching the data services of the data platform and enhancing the data service capabilities of the data platform.

[0063] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0065] Figure 1 is a schematic diagram showing an application scenario according to an exemplary embodiment;

[0066] Figure 2 A schematic diagram of a data service architecture according to an exemplary embodiment;

[0067] Figure 3 Another schematic diagram of a data service architecture according to an exemplary embodiment;

[0068] Figure 4 A flowchart of creating a strongly typed data service interface according to an exemplary embodiment;

[0069] Figure 5a is a schematic diagram of a creation interface of a data service interface according to an exemplary embodiment;

[0070] Figure 5b is another schematic diagram of a creation interface of a data service interface according to an exemplary embodiment;

[0071] Figure 5c is another schematic diagram of a creation interface of a data service interface according to an exemplary embodiment;

[0072] Figure 6 Another flow chart of creating a strongly typed data service interface according to an exemplary embodiment;

[0073] Figure 7 A flowchart of a method for processing a data service according to an exemplary embodiment;

[0074] Figure 8a is a structural diagram of a data service processing device according to an exemplary embodiment;

[0075] Figure 8b is another structural schematic diagram of a data service processing device according to an exemplary embodiment;

[0076] Fig. 9 It is a schematic diagram of the structure of a computing device according to an exemplary embodiment. DETAILED DESCRIPTION

[0077] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0078] The user device information (such as user device information, information stored on the device, etc.), user personal information (such as user biometric information, user name, nickname, geographic location, etc.), information on interaction with third-party software, and user operation behavior information involved in this disclosure are all collected with the user's authorization and subsequently processed or analyzed.

[0079] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0080] In the description of the present disclosure, unless otherwise specified, "plurality" or "several" means two or more.

[0081] As mentioned above, the data platform in the related technology can only provide data call services for weakly typed data, which may not meet the requirements of high business processing efficiency for some businesses. In view of this, the present disclosure provides a technical solution that supports call services for strongly typed data, in which the data platform can dynamically create a strongly typed data service interface (such as an API interface), and based on the created strongly typed API, it can provide strongly typed data calls. On the basis of traditional calls that support weakly typed data, new types of call data are added, enriching the data services of the data platform, enhancing the data service capabilities of the data platform, and thus improving the business processing efficiency of the business party.

[0082] In order to better understand the technical solutions provided by the embodiments of the present disclosure, the following briefly introduces the application scenarios to which the technical solutions provided by the embodiments of the present disclosure are applicable. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of the present disclosure and are not intended to limit the present disclosure. In specific implementation, the technical solutions provided by the embodiments of the present disclosure can be flexibly applied according to actual needs.

[0083] See also Figure 1 The application scenario shown includes a data platform and a business system including multiple business parties. The data platform is, for example, a big data platform. The data platform provides data service interfaces, such as API-type call interfaces. Business systems (specifically, various business parties in the business system) can request data from the data platform by calling these data service interfaces, thereby completing business processing. In other words, the data platform can provide data services for business systems, and data servitization is an important export of the data platform. Data is serviced in the form of API interfaces, opening the data produced by the big data platform to business systems, empowering business systems, and forming a closed data link loop.

[0084] Specifically, raw data can enter the data platform from the business system, and then generate a lot of result data after a series of processing. The business system can request to call these result data through the API interface provided by the data platform, and then complete the business processing. For example, One Service (a data service method) is to open data reading services to the business system in the form of a Remote Procedure Call Protocol (RPC) interface. The data service corresponding to One Service is an open data service interface built on One Data and One Entity. Overall, One Service is committed to realizing unified data services, allowing data to be reused rather than copied, One Data is committed to achieving data standards and unification, making data an asset rather than a cost, and One Entity is committed to achieving entity unification, allowing data to be integrated rather than existing as isolated islands.

[0085] based on Figure 1 For application scenarios, the data platform provides a strongly typed data service interface. Each business party can call this type of data service interface to request strongly typed data from the data platform. After obtaining the strongly typed result data returned by the data platform, they can directly use this result data to execute business, thereby improving business processing efficiency.

[0086] The data platform may be an independent physical server, a server cluster or a distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. The business party may be a client device, or may be understood as a client program for processing business, which is not limited in the embodiments of the present disclosure.

[0087] To further illustrate the technical solution provided by the embodiments of the present disclosure, this is described in detail below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of the present disclosure provide method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on routine or no creative labor. In the steps where there is no necessary causal relationship logically, the execution order of these steps is not limited to the execution order provided by the embodiments of the present disclosure. The method may be executed in the order of the method shown in the embodiments or drawings or in parallel during the actual processing process or when the device is executed.

[0088] To facilitate understanding of the data service solution in the embodiment of the present disclosure, the following first combines Figure 2 and Figure 3 Describe the overall architecture of the data service.

[0089] See also Figure 2 As shown, Figure 2 The schematic diagram of the overall business architecture for data services includes the business layer, data services, data entities, data modeling / development, and data storage. The business layer can also be understood as the application layer. Users interact with data directly through the data platform of the business layer. The business layer can include short video services, live broadcast services, game services, e-commerce services, and social services, etc. The data service layer can provide services such as intelligent data retrieval, asset access, and metadata access. The data entity layer is some specific data, such as user portrait data, user grouping data, content portrait data, behavior data, joint indicators, feature data, and other data. The data modeling / development layer is the modeling and development of data services through different data processing tools. Data storage is used to store data generated during the data service process and provide data storage capabilities. Data storage can include storage media of multiple storage types, such as low-speed cache, medium-speed cache, and high-speed cache according to cache efficiency. Storage areas of different storage types can be selected according to different data storage requirements.

[0090] See also Figure 3 As shown, Figure 3The overall structure of the data service in the embodiment of the present disclosure. Among them, the online service can be understood as Figure 2 The business layer in the data access layer is used to provide a data service interface for the business system. Specifically, it can provide a strongly typed access interface or a weakly typed access interface. In addition, it can support structured query language (SQL) reading, using SQL as the data retrieval interface to meet very flexible data retrieval requirements, and also supports streaming data reading. In addition, it can also perform resource and traffic management, as well as authentication and auditing of business parties, etc. The data exchange layer is used to realize data exchange between different storage media to realize data migration between different storage media; data storage and Figure 2 The data storage in is understood in the same way. For example, the low-speed cache may include Hive and distributed file system (Hadoop Distributed File System, HDFS), the medium-speed cache may include Pika, HBase, ClickHouse, Druid, ES, and the high-speed cache may include Redis, Memcached, etc.; SchemaService is an independent service, which is not only called by One Service, but also by other services. For example, Data Exchange and Streaming Service will also develop their own services based on Schema Service. In the embodiment of the present disclosure, the strongly typed data service interface is dynamically created by calling the Schema Service.

[0091] Above Figure 2 and Figure 3 This is to explain the overall architecture of the data service in the present disclosure. Further, the data service method in the present disclosure is introduced below. As mentioned above, the data platform in the present disclosure can provide data call services for strongly typed data. Based on this, the creation process of the strongly typed data service interface is first introduced below, and then the interface call and data request process based on the created strongly typed data service interface is introduced.

[0092] See also Figure 4 As shown, Figure 4 is a flowchart of creating a strongly typed data service interface in an embodiment of the present disclosure, Figure 4 The process is described as follows.

[0093] Step 401: Acquire interface creation information inputted into the interface creation interface, the interface creation information including a data source identifier and conversion parameter configuration information, the conversion parameter configuration information being used to indicate a target field corresponding to a request parameter and / or return parameter to be converted.

[0094] For example, when creating an API interface, the creator can open a creation interface, for example, the interface creation interface is called an interface creation interface. Figure 5a , Figure 5b , Figure 5c Understand. Figure 5a As shown, the creator can fill in the API creator, the second person in charge of the business, the Chinese name of the API, the importance of the API, the peak query rate per second (QPS) of the interface, and other information in the interface creation interface. Figure 5b You can select the data source and the fields in the data source that need to be converted. For example, Figure 5b In the example, the selected data source is "HIVE", the fields set as request parameters are uid, name, and address, the fields set as return parameters are phone, age, and clicks, and Figure 5c You need to set the estimated amount of synchronized data and the life cycle of the API.

[0095] like Figure 5a , Figure 5b , Figure 5c The information entered in the interface creation interface can be understood as interface creation information, which includes a data source identifier such as Figure 5b The conversion parameter configuration information indicates, for example, Figure 5b Select the relevant fields to be set as request parameters and return parameters, that is, which fields need to be set as request parameters and which fields need to be set as return parameters.

[0096] Step 402: calling a strong type generation service to convert the data corresponding to the target field in the source data indicated by the data source identifier into strongly typed data to obtain a data conversion result.

[0097] The creator follows the creation process and enters relevant API creation information in multiple interface creation interfaces, such as Figure 5c As shown, you can click "Submit Application". Further, the creation device (such as a server) can call the strong type generation service to generate a strong type description for the request parameters and return parameters indicated by the aforementioned conversion parameter configuration information. Specifically, the data included in the fields corresponding to these parameters can be converted into strong type data, and then the data conversion results corresponding to these fields can be obtained. The strong type generation service, for example, is the aforementioned Figure 3The SchemaService mentioned in the SchemaService, or other services that can convert data into strongly typed data types.

[0098] Step 403: Create a data service interface according to the interface creation code and the data conversion result.

[0099] After obtaining the data conversion result, the interface creation code (eg, API creation code) can be called again, combined with the data conversion result to automatically generate the API code logic, and then obtain the newly created API, ie, the data service interface.

[0100] Specifically, for example, the core logic of a strongly typed API can be automatically generated according to the following code flow:

[0101] 1. One Service submits Schema meta information (including request parameters, return parameters, etc.) to Schema Service.

[0102] 2. Schema Service automatically generates proto description files and descriptor descriptors.

[0103] 3. Schema Service automatically compiles the .proto file and generates code, which can be in Java / Python / C++ / ... and other formats.

[0104] 4. Schema Service publishes the generated code to the Nexus private server.

[0105] 5. One Service references the code automatically generated by Schema Service to automatically generate API client code.

[0106] 6. One Service publishes the API client software development kit (SDK) to the Nexus private server.

[0107] 7. The business system references the API client through the Nexus private server to complete the access to the big data service. After the data corresponding to the target field is converted into strongly typed data by calling the Schema Service, the data needs to be stored. Specifically, the interface query parameter threshold (for example, Figure 5aThe interface QPS peak in the data) is used to determine the cache type used to store the data, for example, the target cache type, and then a target storage unit with the target cache type is selected from the cache cluster, and the converted strongly typed data is stored in the selected target storage unit. In other words, the corresponding appropriate type of storage medium can be selected according to the interface query parameter threshold set by the creator, so that the later reading requirements of the data can be met.

[0108] Select a target storage unit whose cache type is the target cache type from the cache cluster. One optional method is to determine candidate storage units whose cache type is the target cache type from the cache cluster, and select a storage unit whose storage capacity can store the converted strongly typed data from the candidate storage units as the target storage unit; another optional method is that if the capacity of the initial storage unit whose cache type is the target cache type determined in the cache cluster is insufficient to store the converted strongly typed data, the initial storage unit is expanded, and the expanded initial storage unit is determined as the target storage unit. That is to say, when the capacity of the selected storage unit of the type meets the requirements for storing the converted strongly typed data, the selection can be made randomly or by using other sorting strategies, which can improve the utilization rate of the storage unit. When the capacity of the selected storage unit of the type meets the requirements for storing the converted strongly typed data, the capacity can be expanded first and then stored. The cache capacity is evaluated according to the data, resources are applied for reasonably, waste is reduced, and necessary storage requirements are met at the same time.

[0109] In specific implementation, the interface importance level indication information (eg Figure 5a The interface importance level indicated by the “importance” in the interface description (in the “importance”) is used to determine the corresponding target group from multiple interface groups. The interface importance levels of each interface group are different, and then the newly created data service interface is divided into the corresponding target group. In other words, after creating the API, it can be reasonably grouped according to the importance level of the API. For example, very important APIs can be divided into one group, important APIs can be divided into another group, and generally important APIs can be divided into another group. By dividing APIs of different importance levels into the same group, each API can be managed in a coordinated manner according to its importance. At the same time, APIs of different importance levels can also be deployed on different machines, that is, different hardware resources can be configured for APIs of different importance levels. For example, a very important API group can be deployed on a machine with better hardware resources to achieve hard isolation between APIs. This can ensure that very important APIs can be called in large quantities at any time without blocking, so as to meet the calling requirements of very important APIs and improve the effectiveness of data calling services.

[0110] See also Figure 6Another flowchart for creating a strongly typed API is shown in FIG. Figure 6 The following is the process of calling the Schema service to automatically create a strongly typed API. Figure 6 illustrate.

[0111] 1. After the user submits a new (i.e., creates) API application on the interface and passes basic parameter verification, the job status can be set to NEW.

[0112] 2. The background thread scans the API creation tasks newly applied for by the user, adds or associates the deployment server, updates the QPS value carried by the server according to the QPS value filled in by the user, and checks whether capacity expansion is required.

[0113] 3. After the service is determined, the storage engine is intelligently selected based on the QPS value. One department may correspond to multiple clusters. Specifically, you can decide which cluster to choose based on the amount of data. If the cluster capacity is not appropriate, you can reapply for the cluster or apply for capacity expansion.

[0114] 4. After steps 2 and 3 are completed, the job enters the APPROVING state and waits for review. After the review is completed, the job status is changed to APPROVED. For example, the job mainly reviews APIs with particularly high QPS values ​​and large storage usage.

[0115] 5. The background thread scans the API jobs in the APPROVED state, obtains the proto class to call the Schema service, generates a strongly typed description for the request parameters and return results, and then references the strongly typed description to automatically generate the client code, and then automatically generates the API based on the client code.

[0116] 6. Call the data exchange service to transfer data (from the low-speed storage system to the high-speed storage system), obtain sample data, generate test code, and execute API test. If the test passes, the record status is TEST_API_DONE. If the test fails, an alarm can also be issued and the job status can be updated.

[0117] 7. After the test passes, wait for the data to be written. Specifically, you can estimate the writing time based on the amount of data in the API, intermittently check whether the data has been written, and wait for the data to be written.

[0118] 8. After the data is imported, rely on the authentication service to authenticate the API, such as using the token service to authenticate the API.

[0119] 9. Submit the client code, automatically publish the client, set the job status to PUBLISHED, and notify the user that the interface has been successfully created, such as sending a notification message to the user or directly displaying it on the creation interface.

[0120] After the creation process of the strongly typed data service interface described above, the following Figure 7 Describes the process of calling a strongly typed data service interface to implement a data request.

[0121] See also Figure 7 As shown, Figure 7 The present invention is a flowchart of a method for processing a data service according to an embodiment of the present invention. The method can be executed by a data platform, such as a server corresponding to a big data platform, and the data platform can provide data services. The flowchart of the method for processing a data service in the present invention is described as follows.

[0122] Step 701: Receive a call request initiated by a service user by calling a data service interface, wherein the data service interface is a pre-created strongly typed call interface, the associated data corresponding to the data service interface is a strongly typed description method, and the call request includes target request parameters.

[0123] The service user is the subject that needs to use the data service, such as Figure 1 Any business party in the call request, and the target request parameter included in the call request is, for example, Figure 5b The request parameter used to indicate the field uid, or the request parameter used to indicate the fields uid and address.

[0124] Step 702: In response to the call request, target data corresponding to the target request parameters is determined from the associated data.

[0125] As mentioned earlier, during the creation of the data service interface, the corresponding source data is associated, and the strongly typed data service interface created has corresponding associated data, and these data are described in a strongly typed manner. The data requested by the service user when calling the data service interface is included in these associated data, so the target data corresponding to the target request parameters determined by the data platform from the associated data is naturally also strongly typed data.

[0126] Step 703: Send the target data to the service user.

[0127] Furthermore, the service user can receive the target data described by strong types, and then directly process the target data to execute the corresponding business. Since the service user does not need to parse the target data but can use it directly, this can improve the business processing efficiency of the service user.

[0128] After receiving the call request initiated by the service user, the data platform can first determine whether the call frequency of the data service interface within the predetermined time is less than the predetermined threshold. If the call frequency of the data service interface within the predetermined time is not less than the predetermined threshold, the response to the call request can be temporarily stopped to limit the call of the interface and realize the soft isolation of the API. In this way, it can be ensured as much as possible that multiple call requests do not affect each other to ensure the effectiveness and security of the interface call. If the call frequency of the data service interface within the predetermined time is less than the predetermined threshold, it can be further determined whether the priority of the call request is higher than other requests waiting to be processed. If the priority of the call request is higher than other requests, the call request can be responded to first, that is, the call request is processed first, and other requests are processed after the call request is processed. If the priority of the call request is lower than the priority of other requests to be processed, other requests with higher priorities can be responded to first. In other words, in the process of processing the call request, the order of processing these call requests can be selected according to the priority of the call request, so that the call request with higher priority can be processed earlier and ensure that important business can be executed as soon as possible, thereby improving the effectiveness of business processing.

[0129] In a possible implementation, the call request also includes the user identification of the service user. After receiving the call request, the data platform can determine the set of call interfaces that the user identification has call authority to call. If the data service interface called by the service user belongs to the call interface set, the call request can be responded to. Conversely, if the data service interface called by the service user does not belong to the call interface set, the call request can be refused to be responded to.

[0130] Alternatively, the call request also includes the user identification of the service user. After receiving the call request, the data platform can determine the set of users that have calling authority for the data service interface called by the service user. If the user identification belongs to the user set, the call request is responded to. Otherwise, if the user identification does not belong to the user set, the call request can be refused to be responded to.

[0131] The above two methods are to authenticate the service user through the user identification of the service user. This is to ensure that only service users with calling permissions can call the data service interface to request data. This can ensure the security of the data platform and thus improve the reliability of the business system.

[0132] In the disclosed embodiments, the data platform can dynamically create a strongly typed data service interface. Based on the created strongly typed data service interface, it can provide strongly typed data calls. In addition to the traditional calls that support weakly typed data, new types of called data are added, thereby enriching the data platform's data services and enhancing the data platform's data service capabilities.

[0133] Based on the same concept of the above embodiments of the present disclosure, Figure 8a is a structural block diagram of a data service processing device according to an exemplary embodiment. Figure 8a As shown, the data service processing device includes a receiving unit 801, a responding unit 802 and a sending unit 803. Among them:

[0134] The receiving unit 801 is configured to execute and receive a call request initiated by a service user by calling a data service interface, wherein the data service interface is a pre-created strongly typed call interface, the associated data corresponding to the data service interface is a strongly typed description method, and the call request includes a target request parameter;

[0135] A response unit 802 is configured to execute a response to the call request and determine target data corresponding to the target request parameter from the associated data;

[0136] The sending unit 803 is configured to send the target data to the service user so that the service user executes the service according to the target data.

[0137] In one possible implementation, see Figure 8b As shown, the data service processing device in the embodiment of the present disclosure further includes a creation unit 804, and the creation unit 804 is configured to execute:

[0138] Acquire interface creation information inputted into the interface creation interface, the interface creation information including a data source identifier and conversion parameter configuration information, the conversion parameter configuration information being used to indicate a target field corresponding to a request parameter and / or a return parameter to be converted;

[0139] Calling a strong type generation service to convert data corresponding to the target field in the source data indicated by the data source identifier into strongly typed data to obtain a data conversion result;

[0140] Create a data service interface based on the interface creation code and data conversion results.

[0141] In a possible implementation, the interface creation information also includes an interface query parameter threshold. Figure 8b As shown, the data service processing device in the embodiment of the present disclosure further includes a storage unit 805, and the storage unit 805 is configured to execute:

[0142] Determine the target cache type based on the interface query parameter threshold;

[0143] Select a target storage unit whose cache type is the target cache type from the cache cluster;

[0144] The converted strongly typed data is stored in the target storage unit.

[0145] In a possible implementation, the storage unit 805 is configured to execute:

[0146] Determine candidate storage units whose cache types are the target cache types from the cache cluster, and select a storage unit whose storage capacity can store strongly typed data from the candidate storage units as the target storage unit; or

[0147] If the capacity of the initial storage unit whose cache type is the target cache type determined in the cache cluster is insufficient to store strongly typed data, the initial storage unit is expanded and the expanded initial storage unit is determined as the target storage unit.

[0148] In a possible implementation manner, the interface creation information further includes interface importance level indication information, and the creation unit 804 is configured to execute:

[0149] Determining a corresponding target group from a plurality of interface groups according to the interface importance level indicated by the interface importance level indication information, wherein the interface importance levels of the respective interface groups are different;

[0150] Assign the newly created data service interface to the target group.

[0151] In a possible implementation, the response unit 802 is configured to execute:

[0152] Determine whether the calling frequency of the data service interface within a predetermined time period is less than a predetermined threshold;

[0153] If the calling frequency of the data service interface within the predetermined time period is less than a predetermined threshold, determining whether the priority of the calling request is higher than other requests waiting to be processed;

[0154] If the priority of the call request is higher than other requests, the call request is processed, and other requests are processed after the call request is processed.

[0155] In a possible implementation, the call request also includes a user identifier, and the response unit 802 is configured to execute:

[0156] Determine the call interface set that the user identifier has the call permission for, and if the data service interface belongs to the call interface set, respond to the call request; or,

[0157] Determine the set of users who have the right to call the data service interface, and respond to the call request if the user identifier belongs to the user set.

[0158] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0159] The division of modules in the embodiments of the present disclosure is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present disclosure may be integrated into one processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0160] Based on the same concept as the above embodiments of the present disclosure, the embodiments of the present application further provide a computing device, such as Figure 1 The server deployed in the data platform in the computing device can execute the above Figure 4 , Figure 6 , Figure 7 The method shown includes the following steps. Fig. 9 As shown, the computing device in the embodiment of the present disclosure includes at least one processor 901, and a memory 902 and a communication interface 903 connected to the at least one processor 901. The specific connection medium between the processor 901 and the memory 902 is not limited in the embodiment of the present application. Fig. 9 In the example, the processor 901 and the memory 902 are connected via a bus 900. Fig. 9 The bus 900 is represented by a bold line, and the connection between other components is only for schematic illustration and is not intended to be limiting. The bus 900 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig. 9 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0161] In the embodiment of the present application, the memory 902 stores instructions that can be executed by at least one processor 901. The at least one processor 901 can execute the steps included in the aforementioned data service processing method by executing the instructions stored in the memory 902.

[0162] Among them, the processor 901 is the control center of the computing device, and can use various interfaces and lines to connect various parts of the entire computing device, and through running or executing instructions stored in the memory 902 and calling data stored in the memory 902, various functions of the computing device and processing data, so as to monitor the computing device as a whole. Optionally, the processor 901 may include one or more processing units, and the processor 901 may integrate an application processor and a modem processor, wherein the processor 901 mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 901. In some embodiments, the processor 901 and the memory 902 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on independent chips.

[0163] Processor 901 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware processor to be executed, or a combination of hardware and software modules in the processor can be executed.

[0164] The memory 902 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 902 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 902 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 902 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0165] The communication interface 903 is a transmission interface that can be used for communication. For example, data can be received or sent through the communication interface 903 .

[0166] See also Fig. 9 A further structural diagram of the computing device shown in FIG. 1 , which also includes a basic input / output system (I / O system) 904 for facilitating information transmission between various components within the computing device, and a large-capacity storage device 908 for storing an operating system 905, application programs 906, and other program modules 907.

[0167] The basic input / output system 904 includes a display 909 for displaying information and an input device 910 such as a mouse and a keyboard for user inputting information. The display 909 and the input device 910 are connected to the processor 901 through the basic input / output system 904 connected to the system bus 900. The basic input / output system 904 may also include an input / output controller for receiving and processing inputs from a plurality of other devices such as a keyboard, a mouse, or an electronic stylus. Similarly, the input / output controller also provides output to a display screen, a printer, or other types of output devices.

[0168] The mass storage device 908 is connected to the processor 901 through a mass storage controller (not shown) connected to the system bus 900. The mass storage device 908 and its associated computer readable media provide non-volatile storage for the server package. That is, the mass storage device 908 may include a computer readable medium (not shown) such as a hard disk or a CD-ROM drive.

[0169] According to various embodiments of the present invention, the computing device package can also be connected to a remote computer on the network through a network such as the Internet. That is, the computing device can be connected to the network 911 through the communication interface 903 connected to the system bus 900, or the communication interface 903 can be used to connect to other types of networks or remote computer systems (not shown).

[0170] Based on the same inventive concept, the present disclosure also provides a storage medium, which may be a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the computer executes the steps of the aforementioned data service processing method.

[0171] Based on the same inventive concept, the present disclosure also provides a chip system, which includes a processor and may also include a memory, for implementing the steps of the aforementioned data service processing method. The chip system may be composed of a chip, or may include a chip and other discrete devices.

[0172] In some possible implementations, various aspects of the data service processing method provided by the present disclosure may also be implemented in the form of a program product, which includes program code. When the program product is run on a computing device, the program code is used to enable the computing device to execute the steps of the data service processing method according to various exemplary implementations of the present disclosure described above.

[0173] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0174] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A data service processing method, characterized in that: The method comprises: Receiving a call request initiated by a service user by calling a data service interface, wherein the data service interface is a pre-created strongly typed call interface, the associated data corresponding to the data service interface is a strongly typed description method, and the call request includes a target request parameter; In response to the call request, determining target data corresponding to the target request parameter from the associated data; Sending the target data to the service user so that the service user executes the business according to the target data; Before receiving a call request initiated by a service user by calling a data service interface, obtain an interface query parameter threshold in the interface creation information input into the interface creation interface; determine a target cache type according to the interface query parameter threshold; select a target storage unit whose cache type is the target cache type from the cache cluster; and store the converted strongly typed data in the target storage unit; The data service interface is created in the following way: Acquire interface creation information inputted into the interface creation interface, the interface creation information including a data source identifier and conversion parameter configuration information, the conversion parameter configuration information being used to indicate a target field corresponding to a request parameter and / or a return parameter to be converted; Calling a strong type generation service to convert data corresponding to the target field in the source data indicated by the data source identifier into strongly typed data to obtain a data conversion result; The data service interface is created according to the interface creation code and the data conversion result.

2. The method according to claim 1, characterized in that Selecting a target storage unit whose cache type is the target cache type from the cache cluster includes: Determine candidate storage units whose cache types are the target cache type from the cache cluster, and select a storage unit whose storage capacity can store the strongly typed data from the candidate storage units as the target storage unit; or If the capacity of an initial storage unit whose cache type is the target cache type determined in the cache cluster is insufficient to store the strongly typed data, the initial storage unit is expanded and the expanded initial storage unit is determined as the target storage unit.

3. The method according to claim 1, characterized in that The interface creation information also includes interface importance level indication information. After creating the data service interface according to the interface creation code and the data conversion result, the method further includes: Determining a corresponding target group from a plurality of interface groups according to the interface importance level indicated by the interface importance level indication information, wherein the interface importance levels of the respective interface groups are different; The newly created data service interface is divided into the target group.

4. The method according to any one of claims 1 to 3, characterized in that: Responding to the call request includes: Determining whether the calling frequency of the data service interface within a predetermined time period is less than a predetermined threshold; If the calling frequency of the data service interface within the predetermined time period is less than the predetermined threshold, determining whether the priority of the calling request is higher than other requests waiting to be processed; If the priority of the call request is higher than that of the other requests, the call request is processed, and the other requests are processed after the call request is processed.

5. The method according to any one of claims 1 to 3, characterized in that: The call request also includes a user identifier, and responding to the call request includes: Determine a call interface set that the user identifier has call permission for, and if the data service interface belongs to the call interface set, respond to the call request; or, A set of users having calling authority for the data service interface is determined, and if the user identifier belongs to the set of users, the calling request is responded to.

6. A data service processing device, characterized in that: The device comprises: A receiving unit is configured to execute a call request initiated by a receiving service user by calling a data service interface, wherein the data service interface is a pre-created strongly typed call interface, the associated data corresponding to the data service interface is a strongly typed description method, and the call request includes a target request parameter; A response unit, configured to execute a response to the call request and determine target data corresponding to the target request parameter from the associated data; A sending unit, configured to send the target data to the service user, so that the service user performs a service according to the target data; The storage unit is configured to execute obtaining an interface query parameter threshold in the interface creation information inputted into the interface creation interface; determining a target cache type according to the interface query parameter threshold; selecting a target storage unit whose cache type is the target cache type from the cache cluster; and storing the converted strongly typed data into the target storage unit; The apparatus further comprises a creating unit, wherein the creating unit is configured to execute: Acquire interface creation information inputted into the interface creation interface, the interface creation information including a data source identifier and conversion parameter configuration information, the conversion parameter configuration information being used to indicate a target field corresponding to a request parameter and / or a return parameter to be converted; Calling a strong type generation service to convert data corresponding to the target field in the source data indicated by the data source identifier into strongly typed data to obtain a data conversion result; The data service interface is created according to the interface creation code and the data conversion result.

7. The device according to claim 6, characterized in that The storage unit is configured to perform: Determine candidate storage units whose cache types are the target cache type from the cache cluster, and select a storage unit whose storage capacity can store the strongly typed data from the candidate storage units as the target storage unit; or If the capacity of an initial storage unit whose cache type is the target cache type determined in the cache cluster is insufficient to store the strongly typed data, the initial storage unit is expanded and the expanded initial storage unit is determined as the target storage unit.

8. The device according to claim 7, characterized in that The interface creation information further includes interface importance level indication information, and the creation unit is configured to execute: Determining a corresponding target group from a plurality of interface groups according to the interface importance level indicated by the interface importance level indication information, wherein the interface importance levels of the respective interface groups are different; The newly created data service interface is divided into the target group.

9. The device according to any one of claims 6 to 8, characterized in that: The response unit is configured to perform: Determining whether the calling frequency of the data service interface within a predetermined time period is less than a predetermined threshold; If the calling frequency of the data service interface within the predetermined time period is less than the predetermined threshold, determining whether the priority of the calling request is higher than other requests waiting to be processed; If the priority of the call request is higher than that of the other requests, the call request is processed, and the other requests are processed after the call request is processed.

10. The device according to any one of claims 6 to 8, characterized in that: The call request also includes a user identifier, and the response unit is configured to execute: Determine a call interface set that the user identifier has call permission for, and if the data service interface belongs to the call interface set, respond to the call request; or, A set of users having calling authority for the data service interface is determined, and if the user identifier belongs to the set of users, the calling request is responded to.

11. A computing device, characterized in that: include: A processor, and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the data service processing method according to any one of claims 1-5.

12. A storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of a computing device, the computing device is enabled to execute the data service processing method according to any one of claims 1 to 5.

Images