Consumer-defined service endpoints
AssigneeIntuit Inc.
InventorsBilly Yuen, Ryan M. Bickerstaff
Life of this patent
Estimating the term…
Abstract
The disclosed embodiments provide a system that facilitates data processing. During operation, the system obtains a schema for data accessed using web services provided by multiple endpoints, wherein the schema is provided by a consumer of the data. Next, the system uses the schema to create a custom endpoint for accessing the data. The system then enables, for the consumer, access to the data through the custom endpoint without requiring querying of the multiple endpoints by the consumer.
Claims13
A computer-implemented method for facilitating data processing, comprising:
- obtaining a schema for data accessed using web services provided by multiple endpoints, wherein the schema is provided by a consumer of the data, and wherein the schema includes a query definition which defines entities, records, or fields to be joined using a custom endpoint;
- validating the schema by verifying a syntactic correctness and a structural correctness, resulting in a validated schema;
- after the validating, using the validated schema to create the custom endpoint for accessing the data, wherein using the validated schema to create the custom endpoint for accessing the data comprises:
- using the query definition from the validated schema to construct a query for retrieving the data without using the multiple endpoints;
- creating a first mapping from an entity name associated with the custom endpoint to the query;
- and
- creating a second mapping from an identifier for the consumer to the entity name, wherein the identifier for the consumer comprises either a username or a numerical user identifier;
- and
- enabling, for the consumer, access to the data through the custom endpoint according to the query definition without requiring querying of the multiple endpoints by the consumer.
A system for facilitating data processing, comprising:
- a configuration apparatus configured to:
- obtain a schema for data accessed using web services provided by multiple endpoints, wherein the schema is provided by a consumer of the data, and wherein the schema includes a query definition which defines entities, records, or fields to be joined using a custom endpoint;
- validate the schema by verifying a syntactic correctness and a structural correctness, resulting in a validated schema, resulting in a validated schema;
- and
- after the validating, use the validated schema to create the custom endpoint for accessing the data, wherein using the validated schema to create the custom endpoint for accessing the data comprises:
- using the query definition from the validated schema to construct a query for retrieving the data without using the multiple endpoints;
- creating a first mapping from an entity name associated with the custom endpoint to the query;
- and
- creating a second mapping from an identifier for the consumer to the entity name, wherein the identifier for the consumer comprises either a username or a numerical user identifier;
- and
- an execution apparatus configured to enable, for the consumer, access to the data according to the query definition without requiring querying of the multiple endpoints.
A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for facilitating data processing, comprising:
- obtaining a schema for data accessed using web services provided by multiple endpoints, wherein the schema is provided by a consumer of the data, and wherein the schema includes a query definition which defines entities, records, or fields to be joined using a custom endpoint;
- validating the schema by verifying a syntactic correctness and a structural correctness, resulting in a validated schema, resulting in a validated schema;
- after the validating, using the validated schema to create the custom endpoint for accessing the data, wherein using the validated schema to create the custom endpoint for accessing the data comprises:
- using the query definition from the validated schema to construct a query for retrieving the data without using the multiple endpoints;
- creating a first mapping from an entity name associated with the custom endpoint to the query;
- and
- creating a second mapping from an identifier for the consumer to the entity name, wherein the identifier for the consumer comprises either a username or a numerical user identifier;
- and
- enabling, for the consumer, access to the data according to the query definition through the custom endpoint without requiring querying of the multiple endpoints by the consumer.
Dependencies are inferred from the claim text.