CN113220755B - Method for flexibly generating GraphQL interface based on multi-source data - Google Patents
Method for flexibly generating GraphQL interface based on multi-source data Download PDFInfo
- Publication number
- CN113220755B CN113220755B CN202011574985.0A CN202011574985A CN113220755B CN 113220755 B CN113220755 B CN 113220755B CN 202011574985 A CN202011574985 A CN 202011574985A CN 113220755 B CN113220755 B CN 113220755B
- Authority
- CN
- China
- Prior art keywords
- interface
- data
- graphql
- information
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/42—Syntactic analysis
- G06F8/427—Parsing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Mathematical Physics (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for flexibly generating a GraphQL interface based on multi-source data, which comprises heterogeneous data source management, metadata information extraction, interface configuration management, interface configuration injection and refreshing, service release and name space management. Business personnel input information of the heterogeneous data sources, and metadata information of the relevant tables is collected by using a metadata information extraction function according to the data source information; through the management of interface configuration, the description mode of the data model adopts the links of uniform throughout source data acquisition, data conversion, data open authority limitation, data interface generation, data interface release, client data acquisition and the like; and then packaging the configuration information and injecting the configuration information into the dynamic language background service by combining with the state information of the interface. Based on the interface configuration file, corresponding interface service is dynamically generated under the condition of not restarting the service, corresponding naming spaces are allocated to the interfaces, and data authority is effectively managed through management of the mutually independent naming spaces.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for flexibly generating and releasing a GraphQL interface based on multi-source data.
Background
When a new project is started, most enterprises will often re-structure the system, service analysis, system analysis, module design and table structure design, write basic CRUD codes for various service tables, and construct corresponding Restful API for the previous section. However, once a cross-database interface is needed, architects are required to redesign corresponding database access layers, implement basic codes, and then implement corresponding multi-database CRUD codes and APIs again by service developers.
In the initial stage of service development, under the condition of relatively perfect design, the CRUD change probability is small, but with the development of service, the original service system design needs to be redesigned, or fields are uniformly added or modified to all tables, developers need to redevelop to realize new design, and new APIs are issued.
The method for generating the GraphQL interface based on multi-source data aims to solve the defect that the repeated labor is time-consuming and labor-consuming, the project cost and the development period are seriously influenced by mechanical development, the competitiveness and the project research and development efficiency are rapidly improved, the development cost is reduced, the development period is shortened, and the method can meet new requirements or changes.
The patent CN107885797A discloses a multi-pattern matching method based on structural correlation, which provides a multi-pattern matching method based on structural correlation for solving the problem of multi-pattern matching, and can improve the overall performance of pattern matching on the premise of adding a small amount of extra space based on the structural correlation of pattern. The invention mainly establishes the structure inheritance relationship between the mode diagrams by utilizing the structure correlation between the mode diagrams, represents the mode diagrams which are originally independent from each other into an integral data structure, and reserves the non-repetitive parts of all the mode diagrams which need to be matched. Meanwhile, the sequence of pattern diagram matching is re-planned, so that when the data diagrams are matched, repeated structural parts in the pattern diagrams can be avoided being matched for many times, the time performance of diagram pattern matching is greatly improved, and the purpose of accelerating calculation is achieved.
Patent CN109587212A discloses a method, device and storage device for designing a graph ql-based micro service architecture, the method includes: applying the GraphQL to a micro-service architecture, performing centralized processing on a user request by using the GraphQL, and then sending the request to a management service center; caching a user request by using a specific caching strategy in the GraphQL server to relieve the pressure of the server; and solving the problems of resource repetition and field conflict in the GraphQL server by using an adhesion method, and integrating the resources in the GraphQL server by using an RPC mode. A micro service architecture design device and a storage device based on GraphQL are used for realizing a micro service architecture design method based on GraphQL. The invention has the beneficial effects that: the technical scheme provided by the invention can aggregate multiple requests of the client into one request, thereby reducing the delay caused by multiple requests; and the cache strategy is adopted, so that the server pressure can be reduced.
Patent CN 109413187a discloses a general method for online interactive browsing and analyzing of graph data, which comprises: setting a plurality of interfaces, wherein each interface is provided with a request and a response for interaction; the method comprises the following steps that request and response interaction is carried out between a graph data front end and a graph data rear end through interfaces, when the graph data front end needs to carry out set function processing, a request is sent to the graph data rear end through an interface i corresponding to the function, and the graph data rear end generates a corresponding response according to the request and sends the response to the graph data front end through the interface i; the request is implemented by POST based on HTTP and comprises a command parameter and a JSON parameter, wherein the command parameter is used for specifying the operation required to be carried out, and the JSON parameter is used for specifying the relevant parameters used in the operation; the response is based on HTTP response, the content of a response body is appointed in a response head to be JSON parameter, and the response body comprises an operation instruction processing result sent by the back end of the graph data to the front end of the graph data. According to the application, common functions are abstracted, the difference between different front-end products and different back-end products is shielded by using a middleware method, a bridge is built between a back-end graph database and a front-end display technology of graph data, the universality is enhanced, the interactive browsing and mining problems of a large-scale graph data system can be solved, and the blank of the current tool on the same block is made up to a certain extent.
The patent CN111198678A discloses a method and a device for generating a GraphQL front-end operation interface, and the invention discloses a method and a device for generating a GraphQL front-end operation interface. The disclosed method comprises: displaying information of all types and objects supported by the GraphQL server to a developer through a GUI (graphical user interface); acquiring selected information of a selected object required to be operated by a developer through a GUI; and automatically constructing a front-end operation interface of the GraphQL based on the selected information of the selected object, wherein the type comprises a schema type, the selected information comprises the attribute of the selected field in the selected object and the specific field value of one or more selected fields, and the front-end operation comprises at least one of query, mutation and description. The technical scheme disclosed can quickly generate the front-end operation interface without manually writing codes by developers.
Patent CN110958131A discloses a method for supporting graph ql-based query on a YANG configuration data model, and specifically discloses a Network Management System (NMS) device for managing a plurality of network devices, the device comprising: a memory configured to store data representing a data model of a plurality of network devices managed by the NMS; and one or more processors configured to retrieve data representing the data model, construct a GraphQL model having a plurality of nodes, store, for each node of one network device according to the data model, data representing attributes of the network device associated with a respective node of the GraphQL model according to the data model, receive a GraphQL query including data representing at least one query attribute, determine which node has attributes matching the at least one query attribute, and return data identifying which network device corresponds to a node having attributes matching the at least one query attribute.
It can be seen that, currently, in the prior art, program developers have the following defects in reading and accessing data sources:
1. at present, the types of databases are numerous, so that the types of data sources are also numerous, particularly, a large database or a database with high safety requirements are often encrypted by various data means, and the data sources are not opened to other data sources, and the types of the data sources are different, so that an opener can only use a special data interface of the data to access the data, the interfaces opened by the opener are numerous, and inconvenience is brought to development;
2. when a plurality of database servers are called, the database is usually required to be normally opened for calling the database, and when the database is replaced, the web server is required to be restarted, so that inconvenience is brought to a database access system, and even a data return result is wrong.
In view of the above technical problems, it is desirable to provide a method for flexibly generating a GraphQL interface based on multi-source data, which is capable of accessing multiple types of data simultaneously, so as to reduce system redundancy and reduce the burden of developers. However, the prior art has not provided an effective solution to the above technical problem.
Disclosure of Invention
In view of the limitations and disadvantages of the prior art, an object of the present invention is to provide a method for integrating multi-source data to automatically generate and publish a service interface, so as to solve the problems in the background art.
In order to achieve the purpose, the invention provides the following technical scheme:
the invention provides a method for flexibly generating a GraphQL interface based on multi-source data, which comprises a front end and a server, wherein the front end comprises a business server web and a configuration management service web, and the server comprises a GraphQL service, a configuration service and an executor;
the method for generating the GraphQL interface is characterized by comprising the following steps of:
step S1, heterogeneous data source management:
firstly, a system administrator or a data user inputs information of a data source, wherein the information comprises a database server address, a database port and a database name, and provides user authentication supporting metadata access;
step S2, metadata information extraction:
the program is connected to a specified data source through data source information with related authority, and all metadata information is obtained, wherein the metadata information comprises a database name, a table name and table field information, and the table field information mainly comprises a field name and a field type; the user can select all or part of the information to be used for designating an open service interface, and the program generates a database-level universal metadata description file according to the selection of the user;
step S3, interface configuration management:
the data user can obtain the accessible database, data table and field management interface configuration according to the authority, the interface configuration describes all the information related to the user application interface, and the setting comprises:
step S3.1 interface definition information configuration: the user configures interface information and manages interface states according to service requirements, the user can add an interface, define interface names, select a library and a table based on metadata information acquirable by user authority, and set input and output parameters and filtering conditions of the interface. The user can also modify or delete the definition of the relevant interface;
step S3.2 interface state setting: the interface enabling or disabling state can be set, and the interface becomes effective after being issued;
step S3.3 interface name space setting: setting a naming space to which the interface belongs, and if not, setting the naming space as a Public space by default;
step S4, interface configuration injection:
if the interface is configured to be in the enabled state, organizing a GraphQL Schema related structure by using the dynamic language characteristic and the interface related configuration set by the user, and injecting the GraphQL Schema related structure into the GraphQL Schema under the naming space to which the GraphQL Schema related structure belongs;
step S5, the service releases:
dynamically generating a corresponding interface service code based on the metadata description file and the user specific interface configuration file, constructing a server by using dynamic language characteristics, refreshing the GraphQL Schema under a name space, and immediately releasing a new interface and opening the new interface to a specified user under the condition that a Web server is not restarted;
and step S6, after the graph QL request written by the graph QL request executor based on the dynamic GrahqlQL Schema passes the server-side verification, the request syntax tree is analyzed by the executor to generate a specific SQL statement, the database SQL statement is executed, and the result is returned.
Therefore, through the steps, the latest interface can be automatically generated under the condition of not changing the source code, the service can be released, and the development work task is obviously reduced.
Preferably, the data source management supports a plurality of existing common database types, and the data source information is stored to the server and necessary connectivity detection is carried out.
Preferably, the GraphQL interface is flexibly defined, and provides default query parameters Schema, activation, deactivation and interface version control.
Preferably, the data model and the interface configuration adopt consistency description, so that other service functions can be conveniently expanded through the data model.
Preferably, the interface definition is automatically generated and the data access logic is dynamically injected into the GraphQL Schema to be available for release.
Preferably, a fixed namespace is designated after the interface is generated through namespace isolation, data authority is effectively isolated, authentication is convenient, and when an end user uses the GraphQL due to the isolation of the namespace to which the interface belongs, the end user can pay attention to the service more easily, and the interface document is not too complex due to the too large GraphQL Schema.
Preferably, the GraphQL request executor can actively analyze the syntax and generate a final database execution statement, and execute and return a corresponding result, which is isolated from the service code of the server, thereby facilitating the support of more databases or further performance optimization.
Preferably, the multi-source data is a heterogeneous data source, such as MySQL, SQLite, and PostgreSQL, and the other data sources are extended by means of a patch.
Preferably, the service controller is configured with a data access interface interpreter, the developer sends an interface access request, the data access interface interpreter interprets the access request, the service controller performs data query on a corresponding database to obtain a query result, the data access interface interpreter of the service controller performs data interpretation on the query result and sends the query result to the developer, and the interpreted data is a data type that can be recognized by the developer.
Preferably, the developer does not directly access the data, and the sent access instructions are instructions processed by the interface, so as to prevent viruses from invading the database.
Compared with the prior art, the invention has the beneficial effects that:
1. the method for flexibly generating and releasing the GraphQL interface based on the multi-source data can automatically generate the latest interface without changing the source code, can complete the release of the service, and obviously reduces the development work task.
2. The invention provides a method for flexibly generating and releasing a GraphQL interface based on multi-source data, mainly relates to the technical field of software development and operation, and can generate a corresponding GraphQL interface according to metadata extracted from a data source and the requirements of a data user through a plurality of simple steps without manual intervention of a developer, so that the GraphQL interface can automatically take effect and is opened to the data user, and the working pressure of common developers is greatly reduced.
Drawings
FIG. 1 is a schematic diagram of a multi-source data GraphQL interface generation architecture according to the present invention;
FIG. 2 is a flow chart of the multi-source data GraphQL interface automatic generation service interface of the present invention;
FIG. 3 is a timing diagram of a new interface for business management publishing in accordance with the present invention;
fig. 4 is a timing diagram illustrating the execution of the GraphQL query request according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
The first embodiment is as follows:
referring to fig. 1, the present invention provides a technical solution:
a method for flexibly generating a GraphQL interface based on multi-source data comprises a front end and a server, wherein the front end comprises a business server web and a configuration management service web, and the server comprises a GraphQL service, a configuration service and an executor;
the method for generating the GraphQL interface is characterized by comprising the following steps of:
step S1, heterogeneous data source management:
firstly, a system administrator or a data user inputs information of a data source, wherein the information comprises a database server address, a database port and a database name, and provides user authentication supporting metadata access;
step S2, metadata information extraction:
the program is connected to a specified data source through data source information with related authority, and all metadata information is obtained and comprises a database name, a table name and table field information, wherein the table field information mainly comprises the field name and a field type; the user can select all or part of the information to be used for designating an open service interface, and the program generates a database-level universal metadata description file according to the selection of the user;
step S3, interface configuration management:
the data user can obtain the accessible database, data table and field management interface configuration according to the authority, the interface configuration describes all the information related to the user application interface, and the setting comprises:
step S3.1 interface definition information configuration: the user configures interface information and manages interface states according to service requirements, the user can add an interface, define interface names, select a library and a table based on metadata information acquirable by user authority, and set input and output parameters and filtering conditions of the interface. The user can also modify or delete the definition of the relevant interface;
step S3.2 interface state setting: the interface enabling or disabling state can be set, and the interface becomes effective after being issued;
step S3.3 interface name space setting: setting a naming space to which the interface belongs, and if not, setting the naming space as a Public space by default;
step S4, interface configuration injection:
if the interface is configured to be in the enabled state, organizing a GraphQL Schema related structure by using the dynamic language characteristic and the interface related configuration set by the user, and injecting the GraphQL Schema related structure into the GraphQL Schema under the naming space to which the GraphQL Schema related structure belongs;
step S5, the service releases:
dynamically generating a corresponding interface service code based on the metadata description file and the user specific interface configuration file, constructing a server by using dynamic language characteristics, refreshing the GraphQL Schema under a name space, and immediately releasing a new interface and opening the new interface to a specified user under the condition that a Web server is not restarted;
and step S6, after the graph QL request written by the graph QL request executor based on the dynamic GrahqlQL Schema passes the server-side verification, the request syntax tree is analyzed by the executor to generate a specific SQL statement, the database SQL statement is executed, and the result is returned.
Preferably, the data source management supports a plurality of existing common database types, and the data source information is stored to the server and necessary connectivity detection is carried out.
Preferably, the GraphQL interface is flexibly defined, and provides default query parameters Schema, activation, deactivation and interface version control.
Preferably, the data model and the interface configuration adopt consistency description, so that other service functions can be conveniently expanded through the data model.
Preferably, the interface definition is automatically generated and the data access logic is dynamically injected into the GraphQL Schema to be available for release.
Preferably, a fixed namespace is designated after the interface is generated through namespace isolation, data authority is effectively isolated, authentication is convenient, and when an end user uses the GraphQL due to the isolation of the namespace to which the interface belongs, the end user can pay attention to the service more easily, and the interface document is not too complex due to the too large GraphQL Schema.
Preferably, the GraphQL request executor can actively analyze the syntax and generate a final database execution statement, and execute and return a corresponding result, which is isolated from the service code of the server, thereby facilitating the support of more databases or further performance optimization.
Preferably, the multi-source data is a heterogeneous data source, such as MySQL, SQLite, and PostgreSQL, and the other data sources are extended by means of a patch.
Preferably, the service controller is configured with a data access interface interpreter, the developer sends an interface access request, the data access interface interpreter interprets the access request, the service controller performs data query on a corresponding database to obtain a query result, the data access interface interpreter of the service controller performs data interpretation on the query result and sends the query result to the developer, and the interpreted data is a data type that can be recognized by the developer.
Preferably, the developer does not directly access the data, and the sent access instructions are instructions processed by the interface, so as to prevent viruses from invading the database.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus.
Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and alterations can be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the appended claims and their equivalents.
Claims (9)
1. A method for flexibly generating a GraphQL interface based on multi-source data comprises a front end and a server, wherein the front end comprises a business server web and a configuration management service web, and the server comprises a GraphQL service, a configuration service and an executor;
the method for generating the GraphQL interface is characterized by comprising the following steps of:
step S1, heterogeneous data source management:
firstly, a system administrator or a data user inputs information of a data source, wherein the information comprises a database server address, a database port and a database name, and provides user authentication supporting metadata access;
step S2, metadata information extraction:
the program is connected to a specified data source through data source information with related authority, and all metadata information is obtained, wherein the metadata information comprises a database name, a table name and table field information, and the table field information mainly comprises a field name and a field type; the user can select all or part of the information to be used for designating an open service interface, and the program generates a database-level universal metadata description file according to the selection of the user;
step S3, interface configuration management:
the data user can obtain the accessible database, data table and field according to the authority, and manage the interface configuration, the interface configuration describes all the information related to the user application interface, the setting includes:
step S3.1 interface definition information configuration: the user configures interface information and a management interface state according to the service requirement, the user can newly add an interface, define an interface name, select a library and a table based on metadata information acquirable by user authority, and set input and output parameters and filtering conditions of the interface; the user can also modify or delete the definition of the related interface;
step S3.2 interface state setting: the interface enabling or disabling state can be set, and the interface becomes effective after being issued;
step S3.3 interface name space setting: setting a naming space to which the interface belongs, and if not, setting the naming space as a Public space by default;
step S4, interface configuration injection:
if the interface is configured to be in the enabled state, organizing a GraphQL Schema related structure by using the dynamic language characteristic and the interface related configuration set by the user, and injecting the GraphQL Schema related structure into the GraphQL Schema under the naming space to which the GraphQL Schema related structure belongs;
step S5, the service releases:
dynamically generating a corresponding interface service code based on the metadata description file and the user specific interface configuration file, constructing a server by using dynamic language characteristics, refreshing the GraphQL Schema under a name space, and immediately releasing a new interface and opening the new interface to a specified user under the condition that a Web server is not restarted;
and step S6, after the GraphQL request written by the GrahqlQL request executor based on the dynamic GrahqL Schema is verified by the server, the request syntax tree is analyzed by the executor to generate a specific SQL statement, the database SQL statement is executed, and a result is returned.
2. The method of claim 1, wherein the method comprises the following steps: the data source management supports various existing common database types, and the data source information is stored to the server side and necessary connectivity detection is carried out.
3. The method for flexibly generating the GraphQL interface based on the multi-source data according to claim 1, characterized in that: the GraphQL interface is flexible and variable in definition, provides default query parameters Schema, and controls the starting, stopping and interface version.
4. The method for flexibly generating the GraphQL interface based on the multi-source data according to claim 1, characterized in that: and automatically generating interface definition and dynamically injecting the data access logic into the GraphQL Schema to achieve the purpose of issuing and using.
5. The method for flexibly generating the GraphQL interface based on the multi-source data according to claim 1, characterized in that: and by the isolation of the naming space, the fixed naming space is appointed after the interface is generated, so that the data authority is effectively isolated, and the authentication is convenient.
6. The method for flexibly generating the GraphQL interface based on the multi-source data according to claim 1, characterized in that: the GraphQL request executor can actively analyze the grammar, generate a final database execution statement, execute and return a corresponding result, and is isolated from the service code of the server.
7. The method for flexibly generating the GraphQL interface based on the multi-source data according to claim 1, characterized in that: the multi-source data are heterogeneous data sources, the heterogeneous data sources comprise MySQL, SQLite and PostgreSQL, and other data sources are expanded in a patch mode.
8. The method for flexibly generating the GraphQL interface based on the multi-source data according to claim 1, characterized in that:
the service controller is provided with a data access interface interpreter, a developer sends an interface access request, the data access interface interpreter interprets the access request, the service controller conducts data query on a corresponding database to obtain a query result, the data access interface interpreter of the service controller conducts data interpretation on the query result and sends the query result to the developer, and the interpreted data are data types capable of being recognized by the developer.
9. The method for flexibly generating the GraphQL interface based on the multi-source data according to claim 8, characterized in that: the developer does not directly access the data, and the sent access instructions are the instructions processed by the interface, so that viruses are prevented from invading the database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011574985.0A CN113220755B (en) | 2020-12-28 | 2020-12-28 | Method for flexibly generating GraphQL interface based on multi-source data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011574985.0A CN113220755B (en) | 2020-12-28 | 2020-12-28 | Method for flexibly generating GraphQL interface based on multi-source data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113220755A CN113220755A (en) | 2021-08-06 |
| CN113220755B true CN113220755B (en) | 2022-06-24 |
Family
ID=77085988
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011574985.0A Active CN113220755B (en) | 2020-12-28 | 2020-12-28 | Method for flexibly generating GraphQL interface based on multi-source data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113220755B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114721711B (en) * | 2022-05-19 | 2022-08-09 | 奇秦科技(北京)股份有限公司 | Tool and method for reducing software research and development configuration based on GraphQL |
| CN114996539B (en) * | 2022-07-29 | 2022-11-01 | 昆仑智汇数据科技(北京)有限公司 | Information processing method, device and equipment |
| CN115309566B (en) * | 2022-08-09 | 2023-09-05 | 医利捷(上海)信息科技有限公司 | Dynamic management method and system for service interface |
| CN117172214A (en) * | 2023-11-02 | 2023-12-05 | 企查查科技股份有限公司 | API file conversion method, system and computer storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107817996B (en) * | 2017-10-13 | 2019-04-23 | 贵州白山云科技股份有限公司 | A kind of optimization method and system of GraphQL request |
| US10558671B2 (en) * | 2018-05-01 | 2020-02-11 | Servicenow, Inc. | Modified representational state transfer (REST) application programming interface (API) including a customized GraphQL framework |
| CN109542506B (en) * | 2018-12-06 | 2021-12-31 | 广州及包子信息技术咨询服务有限公司 | System capable of flexibly configuring interface and rapidly delivering service |
| CN111695074A (en) * | 2020-05-28 | 2020-09-22 | 浙江云蚁信息科技有限公司 | Universal Antsot platform and operation method thereof |
-
2020
- 2020-12-28 CN CN202011574985.0A patent/CN113220755B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN113220755A (en) | 2021-08-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113220755B (en) | Method for flexibly generating GraphQL interface based on multi-source data | |
| CN109144994B (en) | Index updating method, system and related device | |
| US9792327B2 (en) | Self-described query execution in a massively parallel SQL execution engine | |
| EP2932370B1 (en) | System and method for performing a transaction in a massively parallel processing database | |
| US9280568B2 (en) | Zero downtime schema evolution | |
| Viennot et al. | Synapse: a microservices architecture for heterogeneous-database web applications | |
| CA3137857A1 (en) | Multi-language fusion query method and multi-model database system | |
| US9971820B2 (en) | Distributed system with accelerator-created containers | |
| CA3115220C (en) | Correlated incremental loading of multiple data sets for an interactive data prep application | |
| CN115374102A (en) | Data processing method and system | |
| US20180365134A1 (en) | Core Data Services Test Double Framework Automation Tool | |
| CN113468149B (en) | Data model development platform | |
| US7752225B2 (en) | Replication and mapping mechanism for recreating memory durations | |
| JP2023546897A (en) | Object processing methods, devices, and computer equipment | |
| Yuan et al. | VDB-MR: MapReduce-based distributed data integration using virtual database | |
| CN116821098A (en) | Data warehouse management method, service system and storage medium | |
| US20230081067A1 (en) | System and method for query acceleration for use with data analytics environments | |
| Liu et al. | A heterogeneous data integration model | |
| CN113886505B (en) | Management system for realizing dynamic modeling based on search engine and relational database | |
| CN110399378A (en) | Database Systems lock Operations Analyst method and device | |
| CN113885970A (en) | Method, system and medium for generating report data based on script | |
| Liu | Corpus‐Based Japanese Reading Teaching Database Cloud Service Model | |
| Anitha et al. | ETL work flow for extract transform loading | |
| Hardwick et al. | On object-oriented databases, materialized views, and concurrent engineering | |
| Wu et al. | Raven: Benchmarking Monetary Expense and Query Efficiency of OLAP Engines on the Cloud |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |