Oracle International Corporation

Naveen Pilli

David Fernando Saes

Scott Alan Deboy

Gordon James Yorke

Arun Kiran Patro

Andrei Korostelev

A technique for creating a GraphQL Application Programing Interface (API) schema is disclosed. The technique includes generating a filter input object for an object defined in a GraphQL API schema. The filter input object provides the ability for a GraphQL API user (i.e., an API developer or an end user) to perform filtering operations in a query operation on schema objects defined in a GraphQL API schema. The filter input object comprises a set of object attributes and a set of custom attributes. The custom attributes provide the ability for an API developer (or an end user) to perform complex filtering operations in a query operation on schema objects defined in a GraphQL API schema. The technique further includes receiving a query operation to be performed and executing the query operation against a backend datasource to obtain a query result. The query result is transmitted to a GraphQL API user.

GraphQL filter design for a GraphQL application programing interface (API) schema

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.

Datasource introspection user interface for GraphQL API schema and resolver generation

Techniques are disclosed to provide automated remediation of services within a distributed computing system. A remediation service may receive an indication to evaluate a level of health of a first service in a distributed computing system. In response, the remediation service may determine a dependency of the first service on a second service. The remediation service can use a monitor plugin corresponding to the second service to obtain a health metric of the second service. Based on the health metric, the remediation service can determine whether the second service is unhealthy. If the second service is unhealthy, the remediation service can perform a remediation task for the second service.

Techniques for automated service monitoring and remediation in a distributed computing system

Techniques are disclosed to provide automated remediation of services within a distributed computing system. A remediation module may be executed in the distributed computing system to monitor one or more services. Each service can have a corresponding monitor plugin that is loaded into the remediation module and configured to allow the remediation module to interface with the services. The monitor plugin may specify the dependencies of its corresponding service and remediation tasks to be performed on the service if it fails. The remediation module may generate a dependency tree for the services using the specified dependencies from each monitor plugin. The remediation module may query a service to obtain the service's health status, and then use the dependency tree to determine whether upstream services on which the unhealthy service depends are also unhealthy. If the upstream services are healthy, the remediation module may automatically perform remediation tasks on the service.

Growing community of inventors

Milton, Canada

Naveen Pilli