Translating graph queries into efficient network protocol requests
US-11055282-B1 · Jul 6, 2021 · US
US12339836B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12339836-B2 |
| Application number | US-202318322352-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 23, 2023 |
| Priority date | May 23, 2023 |
| Publication date | Jun 24, 2025 |
| Grant date | Jun 24, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A technique is disclosed for creating a GraphQL Application Programing Interface (API) schema by introspecting various different types of backend datasources. The technique includes receiving a selection of a datasource type to create a GraphQL API schema and introspecting the selected datasource type to determine a set of individual elements associated with the selected datasource type. The technique involves outputting the set of individual elements associated with the selected datasource type via a User Interface (UI) screen of a computer system. The technique further includes receiving a selection of one more individual elements associated with the selected datasource type via a UI screen of the computer system. The technique includes generating a GraphQL API schema comprising a set of objects and a set of resolver functions based on the selected elements and presenting the GraphQL API schema via a UI screen associated with the computer system.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, by a GraphQL Application Programming Interface (API) design system implemented using one or more computing systems, a selection of a datasource type to create a GraphQL Application Programing Interface (API) schema; processing, by the GraphQL Application Programming Interface (API) design system, the selected datasource type to obtain metadata associated with the selected datasource type, wherein the metadata comprises a set of individual elements associated with the selected datasource type; outputting, by the GraphQL Application Programming Interface (API) design system, the set of individual elements associated with the selected datasource type via a set of one or more User Interface (UI) screens associated with the GraphQL Application Programming Interface (API) design system; receiving, by the GraphQL Application Programming Interface (API) design system, a selection of one or more individual elements from the set of individual elements associated with the selected datasource type via the set of one or more UI screens; processing, by the GraphQL Application Programming Interface (API) design system, the selected one or more individual elements to generate a set of object types for the GraphQL Application Programming Interface (API) schema, a set of object fields associated with the set of object types for the GraphQL Application Programming Interface (API) schema, and a set of queries supported by the set of object types for the GraphQL Application Programming Interface (API) schema; and outputting, by the GraphQL Application Programming Interface (API) design system, via the set of one or more UI screens, the GraphQL API schema for the selected datasource type, the GraphQL API schema comprising the set of object types for the GraphQL Application Programming Interface (API) schema, the set of object fields associated with the set of object types for the GraphQL Application Programming Interface (API) schema, the set of queries supported by the set of object types for the GraphQL Application Programming Interface (API) schema, and a set of resolver functions associated with the set of object types for the GraphQL Application Programming Interface (API) schema. 2. The method of claim 1 , wherein the selected datasource type is a relational database. 3. The method of claim 2 , wherein processing, by the GraphQL Application Programming Interface (API) design system, the selected datasource type comprises introspecting the relational database to determine a set of individual elements associated with the relational database. 4. The method of claim 3 , wherein the set of individual elements associated with the relational database comprise a set of one or more tables within the relational database, a set of one or more columns associated with the set of one or more tables and a set of one or more operations supported by the set of one or more tables and the set of one or more columns. 5. The method of claim 1 , wherein outputting, by the GraphQL Application Programming Interface (API) design system, the set of individual elements associated with the selected datasource type comprises outputting a set of one or more tables associated with a relational database and a set of one or more columns associated with the set of one or more tables via the set of one or more UI screens, wherein the selected datasource type is the relational database. 6. The method of claim 1 , wherein receiving, by the GraphQL Application Programming Interface (API) design system, a selection of one or more individual elements from the set of individual elements associated with the selected datasource type comprises receiving a selection of one or more tables associated with a relational database, wherein the selected datasource type is the relational database. 7. The method of claim 6 , further comprising receiving, by the GraphQL Application Programming Interface (API) design system, a selection of one or more columns associated with the one or more tables and receiving a selection of one or more operations supported by the one or more tables via the set of one or more UI screens. 8. The method of claim 1 , wherein the selected datasource type is a relational database and wherein outputting, by the GraphQL Application Programming Interface (API) design system, the GraphQL API schema for the selected datasource type comprises outputting the GraphQL API schema for the relational database. 9. The method of claim 1 , wherein the selected datasource type is a Representational State Transfer (REST) Application Programing Interface (API) datasource. 10. The method of claim 9 , wherein processing, by the GraphQL Application Programming Interface (API) design system, the selected datasource type comprises introspecting the REST API datasource to determine a set of individual elements associated with the REST API datasource. 11. The method of claim 10 , wherein the set of individual elements associated with the REST API datasource comprise a set of one or more APIs associated with the REST API datasource, one or more query parameters associated with the set of one or more APIs and response information associated with the set of one or more APIs. 12. The method of claim 1 , wherein receiving, by the GraphQL Application Programming Interface (API) design system, the selection of one or more individual elements from the set of individual elements associated with the selected datasource type comprises receiving a selection of one or more APIs associated with a REST API datasource, wherein the selected datasource type is the REST API datasource. 13. The method of claim 1 , further comprising: receiving, by the GraphQL Application Programming Interface (API) design system, a selection of an object type from the set of object types defined in the GraphQL API schema via the set of one or more UI screens; receiving, by the GraphQL Application Programming Interface (API) design system, an indication to edit a resolver function associated with the selected object type; and responsive to receiving the indication, presenting, by the GraphQL Application Programming Interface (API) design system, structural information associated with the selected object type. 14. The method of claim 13 , further comprising: receiving, by the GraphQL Application Programming Interface (API) design system, a modification to the structural information associated with the selected object type; based on the modification, editing, by the GraphQL Application Programming Interface (API) design system, the resolver function associated with the selected object type; and publishing, by the GraphQL Application Programming Interface (API) design system, a modified GraphQL API schema via the set of one or more UI screens. 15. A system comprising: a memory; and one or more processors configured to perform processing, the processing comprising: receiving a selection of a datasource type to create a GraphQL Application Programing Interface (API) schema; processing the selected datasource type to obtain metadata associated with the selected datasource type, wherein the metadata comprises a set of individual elements associated with the selected datasource type; outputting the set of individual elements associated with the selected datasource type via a set of one or more User Interface (UI) screens associated with the system; receiving a selection of one or more individual elements from the set of individual elements associated with the selected datasource type via the set of one or more UI screens; processing the selected one or more individu
Schema design and management · CPC title
Interactive query statement specification based on a database schema · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.