TW201944232A - Method and system of obtaining resources using unified composite query language - Google Patents

Abstract

A method and a system of obtaining resources using unified composite query language are provided. In at least some embodiments, an intermediary module of CQL execution receives a unified composite query language document describing a resource structure of multiple resources to determine whether the whole resources are analyzed. According to the result of analysis, the intermediary module calls related applications to offer the resources, and then sends the resource to users, thereby improving the efficiency of access to resources.

Description

   Method and system for obtaining resources using unified aggregation query language   

The invention relates to a technology for obtaining application program resources, in particular to a method and system for obtaining microservice-type application program resources using a unified aggregation query language.

Traditionally, when a user wants to access the resources of a server back-end application (such as a micro-service-type application), the user must first understand what applications are on the server back-end and the application programming API (Application Programming Interface) specifications and application API usage.

Then, the user can make a request to the server to access the application resource (composite resource) according to the calling (communication) methods of different application APIs. After the service server receives the request, it can call the corresponding through an individual imperative syntax. Application API to provide application resources.

After that, after the server receives all the application resources returned by the corresponding application API, it combines all the application resources into a composite resource required by the user and sends it to the user.

In this way, the generation of composite resources requires users to understand the API specifications and usage methods of the server's back-end applications, so that users cannot focus on the presentation of composite resources (that is, the resource structure).

In addition, once the API specification of the server back-end application changes, a series of imperative syntax related to composite resources must be redesigned and compiled, resulting in low reusability of the aforementioned generation method.

In view of the foregoing problems, it is really necessary to provide a method and system for effectively obtaining the composite resources required by users to solve the problems faced by users.

In view of the problems existing in the prior art, the present invention discloses a method and system for obtaining resources using a unified aggregation query language. Compared with the prior art, which uses an imperative syntax to combine the required composite resources, an embodiment of the present invention discloses the use of a unified aggregation query language file to describe the structure of the required composite resources, and then analyzes This document achieves the same purpose, users do not need to understand the details of the use of each service API, thereby improving the execution efficiency of the service system.

An embodiment of the present invention provides a method for obtaining resources using a unified aggregation query language, including the following steps: (1) receiving a unified aggregation query language file, which describes a resource structure of a plurality of resources; (2) based on the resource structure To determine whether the plurality of resources in the unified aggregation query language file are all resolved; (3) if the plurality of resources have been completely resolved, obtain a first analysis result from a CQL file database to call the first A first application program group related to the analysis result, thereby providing a plurality of first resources. Conversely, if the plurality of resources are not completely parsed, the plurality of resources are parsed to generate a second analysis result, and the second analysis result is called. A related second application group provides multiple second resources.

In another embodiment, the plurality of first resources or the plurality of second resources are combined into a composite resource.

In another embodiment, step (3) includes the following steps: (i) translating the unified aggregation query language file into an abstract syntax tree (Abstract Syntax Tree); and (ii) judging the complex number based on the abstract syntax tree Whether the resource has been resolved to call the second application group, thereby providing the plurality of second resources.

In another embodiment, in step (ii), it is determined whether the complex resource has been parsed in an iterative manner or in a parallel manner.

In another embodiment, an API (Application Programming Interface) communication with the first application group is used to call the first application group; and / or an API with the second application group is used The communication method is to call the second application group.

In another embodiment, the first application group and / or the second application group are called in an iterative manner.

In another embodiment, the first application group and / or the second application group are called in a parallel manner.

In another embodiment, the first application group and / or the second application group are composed of a plurality of microservices applications.

In another embodiment, the unified aggregation query language file is a declarative description language file based on JSON (JavaScript Object Notation).

Another embodiment of the present invention provides a system for obtaining resources using a unified aggregation query language, including: a unified aggregation query language file execution module that receives a unified aggregation query language file describing a resource structure of a plurality of resources, wherein If the unified aggregation query language file execution module has ever parsed the unified aggregation query language file, the unified aggregation query language file execution module obtains a first parsing result from a CQL file database to call and the first A first application group related to the analysis result, thereby providing a plurality of first resources. Conversely, if the unified aggregation query language file execution module has not parsed the unified aggregation query language file, the unified aggregation query language file execution module The group parses the plurality of resources to generate a second analysis result, and calls a second application program group related to the second analysis result to provide a plurality of second resources.

In another embodiment, the unified aggregation query language file execution module combines the plurality of first resources or the plurality of second resources into a composite resource.

In another embodiment, the unified aggregation query language file execution module communicates with the API of the first application program group to call the first application program group, and the unified aggregation query language file execution module is related to API communication of the second application group to call the second application group.

In another embodiment, the unified aggregation query language document execution module uses an iterative method or a parallel method to call the first application group and / or the second application group.

In another embodiment, the first application group and / or the second application group are composed of a plurality of microservices applications.

In another embodiment, the unified aggregation query language file is a JSON-based declarative description language file.

It should be understood that the subject matter described above may be implemented as a computer-controlled device, computer program, computing system, or as a product, such as a computer-readable storage medium.

In order to make the above features and advantages of the present invention more comprehensible, embodiments are described below in detail with reference to the accompanying drawings. Additional features and advantages of the present invention will be partially explained in the following description, and these features and advantages will be partially obvious from the description, or may be learned through practice of the present invention. The features and advantages of the invention are realized and achieved by means of elements and combinations specifically pointed out in the scope of the patent application. It should be understood that both the foregoing general description and the following detailed description are merely exemplary and explanatory and are not intended to limit the scope of the invention as claimed.

101‧‧‧CQL file

102‧‧‧Order resource structure

103‧‧‧Customer resource structure

104‧‧‧Product Resource Structure

105‧‧‧Credit resource structure

106‧‧‧CQL file

107‧‧‧CQL file

108‧‧‧CQL execution mediation module

109 ~ 111‧‧‧ microservice application

S112 ~ S119‧‧‧step

FIG. 1 is a unified aggregate query language file and various composite resource structures in the file according to an embodiment of the present invention; FIG. 2 is a composite resource structure with conditional statements according to an embodiment of the present invention FIG. 3 is a schematic diagram of a CQL execution environment according to an embodiment of the present invention; and FIG. 4 is a flowchart of generating a composite resource according to an embodiment of the present invention.

The following describes the embodiments of the present invention with specific specific implementation forms. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this description, and can also be implemented by other different specific implementation forms. Or apply.

In addition, some or all of the operations of the methods or processes herein and / or substantially equivalent operations may be performed by executing computer-readable instructions (as defined herein) included on a computer storage medium. Variations of the terms "computer-readable instructions" and "computer-readable instructions" used in the scope of the description and patent applications are used herein to include routines, applications, application modules, program modules, Programs, components, data structures, algorithms, and more. Computer-readable instructions can be implemented on a variety of system configurations, including single-processor or multi-processor systems, mini computers, mainframe computers, personal computers, palm computing devices, programmable microprocessor-based consumer electronics devices Or a combination of those and so on.

Therefore, it should be understood that the logic operations described herein are implemented as a computer-implemented sequence of actions or a program module executed on a computing system and / or as an interconnected machine logic circuit or circuit module within a computing system. Implementation is a matter of choice depending on the performance of the computing system and other requirements. Therefore, the logical operations described herein are referred to variously as states, operations, structural devices, actions, or modules. These operations, structural devices, actions, and modules can be implemented in software, in firmware, in special-purpose digital logic, and in any combination of the foregoing.

Reference is now made to FIG. 1, which illustrates a unified aggregation query language file and various composite resource structures in the file according to an embodiment of the present invention.

The Unified Composite Query Language (CQL) file (such as: CQL file 101) in the present invention can be used to describe various composite resource structures. The composite resource structure is composed of various resource items (such as main resource items). , Secondary resource projects, secondary resource projects, etc.). The resource item can describe various resources distributed in various applications (eg, microservices applications).

In one embodiment, the CQL file 101 can be implemented as a JSON (JavaScript Object Notation) -based declarative description language file.

In one embodiment, the CQL file 101 may be parsed (eg, for a main resource item, etc.) to obtain a parsed resource structure, and an application program related to the parsed resource structure may be called to obtain a corresponding resource.

Thereafter, the CQL file 101 can be repeatedly analyzed in parallel or iteratively (for example, for other major resource items, for secondary resource items, and secondary resource items, etc.) to obtain a resolved resource structure. , And call the app to get the corresponding resource until it cannot be further parsed. Finally, you can get the resources you want.

In this way, when the user requests an application (such as a microservice application) resource from the server (system), the system can effectively hide the call details of the application's API (Application Programming Interface) and allow the user to Request application resources in a way that is close to the needs of the terminal (ie, in a composite resource structure).

In addition, through the use of a composite resource structure, even if the API specifications of the application program are slightly changed, the system can effectively access the application resource, thereby providing a fault tolerance mechanism for resource access.

Now, returning to FIG. 1, the CQL file 101 can describe the resource structure related to order resources (such as resource items such as orders, customers, credits, and products in various microservices).

In CQL Document 101, the item "Order" can be considered as a major resource item; the items "Customer" and "Product" can be considered as a minor resource item under the major resource item "Order"; and the item "Credit" is considered a minor resource item The "resources" item under "Customer".

In addition, if each resource item is analyzed, it is mainly based on the similarity of the resource structure. If it is found that the order resources provided by the application service (application program) conform to the attribute structure described in the CQL file, the item in the CQL file 101 "Can be resolved into the order resource structure 102; the item" customer "can be resolved into the customer resource structure 103; the item" product "can be resolved into the product resource structure 104; and the item" credit "can be resolved into the credit resource structure 105.

In the order resource structure 102, the item "order" can be regarded as the main resource item in the order resource structure 102, and the item "order" includes "order number (orderID)", "customer number (custNo)", and "product" Grade secondary resource project.

In the customer resource structure 103, the item "customer" can be regarded as the main resource item in the customer resource structure 103, and the item "customer" includes "number (no)", "name", "age" Grade secondary resource project.

In the product resource structure 104, the item "product" can be regarded as the main resource item in the product resource structure 104, and the item "product" includes secondary resource items such as "type" and "price".

Please refer to FIG. 2, which illustrates a unified aggregate query language file of a composite resource structure with conditional statements according to an embodiment of the present invention.

Compared to the CQL file 101 shown in FIG. 1, a conditional statement is added to the CQL file 106 shown in FIG. 2 to limit the range corresponding to the resource.

For example, the item "No" under the item "Customer" in the CQL file 106 can be set as the "Customer Number (custNo)" of the item "Order". Here, the XML Path syntax or similar syntax (eg, JSON Path syntax) can be used to describe this setting. For example: Use the expression "no: $. Order.custNo" to specify the relevant conditions for binding the item "Customer" to the item "Order".

In an embodiment, a JSON Path may also be used to indicate a parsing path of an item. For example: The expression "$" means to search from the top-level item (such as the root node in the JSON Path structure). The expression "$ .Order.custNo" represents the value of the custNo node under the order node under the root node (that is, the item "customer number (custNo)"). The expression "no: $ .Order.custNo" means that the secondary item "No." under the item "Customer" must be equal to the secondary item "Customer Number (custNo)" under the item "Order".

With the aforementioned notation, the relevance between items (resources) can be easily indicated. On the other hand, we can use the notation "?" To get information about a specific item.

For example, we could use the notation "price :?" under the item "product". In this way, although the information of the item "price" is not displayed in the current item "product", the related information of the item "price" can be obtained through subsequent resource analysis and calling the application related to the item "price" Information (resources).

Please refer to FIG. 3, which is a schematic diagram of a CQL execution environment according to an embodiment of the present invention.

The CQL execution intermediary module 108 may receive the CQL file 107 to parse the CQL file 107, and then request related resources from the corresponding microservice application 109, microservice application 110, and microservice application 111 according to the analysis result.

In an embodiment, the resources requested from the microservice application 109, the microservice application 110, and the microservice application 111 have a sequential relationship, and the CQL execution intermediary module 108 may be iteratively and sequentially Request resources from the microservice application 109, the microservice application 110, and the microservice application 111.

In an embodiment, the resources requested from the microservice application 109, the microservice application 110, and the microservice application 111 have no order relationship with each other, and the CQL execution intermediary module 108 may be in a parallel manner at the same time. Request resources from the microservice application 109, the microservice application 110, and the microservice application 111.

After that, the CQL execution intermediary module 108 then combines the obtained from the microservice application 109, the microservice application 110, and the microservice application 111 into a composite resource that meets the needs of the user, so as to transmit the composite resource to the use. Person side.

In an embodiment, the CQL execution intermediary module 108 may store the analysis process and analysis result of the CQL file 107 and the CQL file 107 in a CQL file database (not shown). Thereafter, if there is a need for analysis of the CQL file 107, the CQL execution intermediary module 108 can directly obtain the analysis process and analysis result of the CQL file 107 from the CQL file database, without performing the analysis of the CQL file 107 again. In order to improve the execution efficiency of the system.

Now, please refer to FIG. 4, which is a flowchart of generating a composite resource according to an embodiment of the present invention.

First, in step S112, a CQL file 107 describing the data structure of the composite resource is received.

Next, in step S113, it is determined whether the composite resource in the CQL file 107 has been resolved (that is, whether the same resource structure has been resolved) according to the resource structure. If the determination result is that the composite resource structure in the CQL file 107 has been parsed, it proceeds to step S117.

In step S117, the CQL execution intermediary module 108 obtains the analysis result of the composite resource structure in the CQL file 107 from the CQL file database, and requests the related resources from the related application group according to the analysis result.

After that, in step S118, the CQL execution intermediary module 108 combines related resources obtained from the application group (eg, multiple microservices) into a composite resource that meets the user's requirements, so as to combine the CQL file 107 The analysis process and analysis results of CQL file 107 are stored in the CQL file database.

In one embodiment, the CQL file database may be an external database. Alternatively, the CQL document database can also be built into the CQL execution intermediation module 108 as part of the CQL execution intermediation module 108.

Next, in step S119, the composite resource is returned to the user terminal, and the process ends.

Now, return to step S113, if the determination result is that the composite resource structure in the CQL file 107 has not been parsed before, it proceeds to step S114.

In step S114, the CQL execution intermediary module 108 translates the CQL file into an Abstract Syntax Tree (AST).

Then, the method proceeds to step S115. At this time, the CQL execution intermediary module 108 determines whether there are unresolved resources in the CQL file (that is, there are unresolved resource structures) according to the abstract syntax tree content. If yes, go to step S116. At this time, the CQL execution intermediary module 108 calls an application group related to the unresolved resources to provide unresolved resources, and continues to parse the CQL file based on the provided resources.

In an embodiment, the CQL execution intermediary module 108 in step S115 may determine the method for determining whether there are still unparsed CQL files 107 according to the abstract syntax tree generation mode (that is, the search mode of the abstract syntax tree). Resources.

For example, when the abstract syntax tree is generated in a breadth-first manner, the CQL execution intermediary module 108 may determine in parallel whether unresolved resources still exist. In contrast, if the abstract syntax tree is generated in a depth-first manner, the CQL execution intermediary module 108 can iteratively determine whether unresolved resources still exist

In one embodiment, the CQL execution intermediary module 108 in steps S116 and S117 may use the API communication with the application group to request related resources from the application group.

In one embodiment, the CQL execution intermediary module 108 in steps S116 and S117 may request related resources from the application group in an iterative manner or an in parallel manner.

In an embodiment, the CQL execution intermediary module 108 in step S116 may return to step S114 after parsing a specific number of resources (eg, one, two, etc.) in the CQL file 107, and repeat the steps. Steps S114 to S116 are performed until there are no longer any unresolved resources in the CQL file 107, or the existing unresolved resources cannot be provided by any application (that is, the resources cannot be parsed further).

After that, in step S118, the CQL execution intermediary module 108 combines the related resources obtained from the application group into a composite resource that meets the user's requirements, so as to analyze and analyze the CQL file 107 and the CQL file 107. Results are stored in a CQL file database.

Finally, in step S119, the composite resource is transmitted back to the user terminal, and the process ends.

Those skilled in the art should understand that in the process of generating composite resources as shown in the foregoing Figure 4, because the application group is called by the CQL execution intermediary module 108 after the unresolved resources are resolved, so Even if the API version of some applications in the application group changes, as long as the resource structure does not have a destructive change, the CQL execution intermediary module 108 can correspondingly call the correct version of the application API, so that it has access to application resources. Fault tolerance mechanism.

The above-mentioned embodiments merely exemplify the principles, features, and effects of the present invention, and are not intended to limit the implementable scope of the present invention. Anyone who is familiar with this technology can perform the above operations without departing from the spirit and scope of the present invention. Modifications and changes to the implementation form. Any equivalent changes and modifications made by using the disclosure of the present invention should still be covered by the scope of patent application. Therefore, the scope of protection of the rights of the present invention should be as listed in the scope of patent application.

Claims (15)

    A method for obtaining resources using a unified aggregation query language includes the following steps: (1) receiving a unified aggregation query language file describing a resource structure of a plurality of resources; (2) judging the unified aggregation query language based on the resource structure Whether the plurality of resources in the file are all parsed; and (3) if the plurality of resources are all parsed, obtain a first parse result from a CQL file database to call a first parsed result related to the first parse result An application group, and then provide a plurality of first resources, and conversely, if the plurality of resources are not completely parsed, the plurality of resources are parsed to generate a second analysis result to call a second application related to the second analysis result Program group, which in turn provides a plurality of second resources.         The method described in item 1 of the patent application scope further comprises combining the plurality of first resources or the plurality of second resources into a composite resource.         According to the method described in item 1 of the patent application scope, step (3) further includes the following steps: (i) translating the unified aggregation query language file into an Abstract Syntax Tree; and (ii) according to the abstraction A syntax tree to determine whether the plurality of resources have been parsed to call the second application group, thereby providing the plurality of second resources.         The method according to item 3 of the scope of patent application, wherein in step (ii), iteratively or in parallel is used to determine whether the complex resource has been resolved.         The method according to any one of claims 1 to 4, wherein the first application group is called by using an API (Application Programming Interface) communication with the first application group; and / Or call the second application group by using API communication with the second application group.         The method according to any one of claims 1 to 4, wherein the first application group and / or the second application group are called in an iterative manner.         The method according to any one of claims 1-4, wherein the first application group and / or the second application group are called in parallel.         The method according to any one of claims 1-4, wherein the first application group and / or the second application group are composed of a plurality of micro-service-type applications.         The method according to any one of claims 1 to 4, wherein the unified aggregation query language file is a JSON (JavaScript Object Notation) -based declarative description language file.         A system for obtaining resources using a unified aggregation query language includes a unified aggregation query language file execution module that receives a unified aggregation query language file describing a resource structure of a plurality of resources, and if the unified aggregation query language file executes a module The team has parsed the unified aggregation query language file, and the unified aggregation query language file execution module obtains a first parsing result from a CQL file database to call a first application program group related to the first parsing result. Group, and then provide a plurality of first resources, otherwise, if the unified aggregation query language file execution module has not parsed the unified aggregation query language file, the unified aggregation query language file execution module parses the plurality of resources to generate a second The analysis result is used to call a second application program group related to the second analysis result, thereby providing a plurality of second resources.         The system according to item 10 of the scope of patent application, wherein the unified aggregation query language file execution module combines the plurality of first resources or the plurality of second resources into a composite resource.         The system according to item 10 of the scope of patent application, wherein the unified aggregation query language document execution module communicates with the API of the first application program group to call the first application program group, and the unified aggregation query The language document execution module communicates with the API of the second application program group to call the second application program group.         The system according to item 10 of the scope of patent application, wherein the unified aggregation query language document execution module uses an iterative method or a parallel method to call the first application group and / or the second application group.         The system according to item 10 of the scope of patent application, wherein the first application program group and / or the second application program group are composed of a plurality of microservice application programs.         The system according to item 10 of the patent application scope, wherein the unified aggregation query language file is a JSON-based declarative description language file.