Self-service composed web APIs
US-9262183-B2 · Feb 16, 2016 · US
US2018004767A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018004767-A1 |
| Application number | US-201615199818-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jun 30, 2016 |
| Priority date | Jun 30, 2016 |
| Publication date | Jan 4, 2018 |
| Grant date | — |
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.
Embodiments are directed to connectors that use a common contract to expose data sources to applications. The common contract provides access to a plurality of different dataset types without requiring the applications to know the specific dataset type used by the data sources.
Opening claim text (preview).
What is claimed is: 1 . A system for connecting applications to services, the system comprising: a processor and memory configured to: provide a connector that uses a common contract to expose a data source to an application, the common contract providing access to a plurality of different dataset types without requiring the application to know the specific dataset type used by the data source. 2 . The system of claim 1 , wherein the connector exposes an application program interface (API) for managing datasets according to the common contract. 3 . The system of claim 2 , wherein the common contract provides a standardized interface to perform Create, Read, Update, Delete (CRUD) operations on the data sources using APIs. 4 . The system of claim 2 , wherein the data source comprises a tabular data resource hierarchy. 5 . The system of claim 4 , wherein the application calls the API to manage tables and items in the data set using the common contract. 6 . The system of claim 2 , wherein the data source comprises a blob data resource hierarchy. 7 . The system of claim 6 , wherein the application calls the API to manage folders and files. 8 . The system of claim 1 , wherein the connector exposes an application program interface (API) for triggering actions when a dataset event is detected. 9 . The system of claim 1 , wherein the connector is a composite connector that exposes application program interfaces (API) for managing data resources using both a tabular data hierarchy and a blob data hierarchy according to the common contract. 10 . The system of claim 1 , further comprising: a distributed computer network hosting a plurality of connectors, wherein each of the connectors is associated with a different data source and exposes an application program interface (API) for managing data on each data source according to the common contract. 11 . A computer-implemented method for connecting applications to services, comprising: providing a connector that uses a common contract to expose a data source to an application; and providing access to a plurality of different dataset types using the common contract without requiring the application to know the specific dataset type used by the data source. 12 . The method of claim 11 , wherein the connector exposes an application program interface (API) for managing datasets according to the common contract. 13 . The method of claim 12 , wherein the common contract provides a standardized interface to perform Create, Read, Update, Delete (CRUD) operations on the data sources using APIs. 14 . The method of claim 12 , wherein the data source comprises a tabular data resource hierarchy. 15 . The method of claim 14 , further comprising: receiving API calls from the application at the connector to manage tables and items in the data set using the common contract. 16 . The method of claim 12 , wherein the data source comprises a blob data resource hierarchy. 17 . The method of claim 16 , further comprising: receiving API calls from the application at the connector to manage folders and files. 18 . The method of claim 1 , further comprising: exposing an application program interface (API) by the connector for triggering actions when a dataset event is detected. 19 . The method of claim 1 , wherein the connector is a composite connector that exposes application program interfaces (API) for managing data resources using both a tabular data hierarchy and a blob data hierarchy according to the common contract. 20 . The method of claim 1 , further comprising: associating a plurality of connectors in a distributed computer network with a different data source; and exposing an application program interface (API) for managing data on each data source according to the common contract.
Large Object storage; Management thereof · CPC title
Updating · CPC title
File or folder operations, e.g. details of user interfaces specifically adapted to file systems · CPC title
Integrating or interfacing systems involving database management systems · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.