System and method for syncing asynchronously received sequential data from disparate sources
US-2024346043-A1 · Oct 17, 2024 · US
US11514070B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11514070-B2 |
| Application number | US-201816235819-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 28, 2018 |
| Priority date | Oct 6, 2018 |
| Publication date | Nov 29, 2022 |
| Grant date | Nov 29, 2022 |
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.
An Application Programming Interface (API) processes object storage requests in an object storage format that are received from client applications. A mapper maps the object storage formatted requests into database statements and executes the statements within a database management system. Results returned from the statements are mapped by the mapper to object-storage constructs and provided to the API in object storage format. The object storage formatted requests are provided from the API to the client applications to satisfy the original client applications' requests.
Opening claim text (preview).
The invention claimed is: 1. A method, comprising: receiving an object storage request from a requesting application with object storage data constructs for an object storage; mapping the object storage request with the object storage data constructs to database statements with database constructs for a database management system (DBMS), wherein the mapping translates the object storage request into the database statements that identify a bucket in the object storage request as a virtual bucket that includes a collection of one or more datasets in the DBMS comprising one or more tables and views, and that identify an object in the object storage request as a virtual object of the virtual bucket that references a subset of the datasets in the DBMS comprising one or more rows that belong to the tables and views; processing the database statements with the database constructs on the DBMS to generate database formatted results; mapping the database formatted results returned from the processing to results in an object storage format with the object storage data constructs to return the bucket and object for the object storage request as the virtual bucket and the virtual object; and providing the results in the object storage format with the object storage data constructs to the requesting application that provided the object storage request. 2. The method of claim 1 , further comprising rendering results that satisfy the object storage request as a dynamically generated database view or a materialized view within the DBMS. 3. The method of claim 1 , wherein the receiving further includes identifying the object storage request as an object storage formatted request. 4. The method of claim 1 , wherein the mapping further includes separating the object storage request into a first request mapped to the database statements and a second request delivered to the object storage. 5. The method of claim 1 , wherein the mapping further includes defining at least some of the database statements as projections of existing database datasets. 6. The method of claim 5 , wherein the defining further includes maintaining bucket identifiers and storage object identifiers provided with the object storage requests with the projections as mappings. 7. The method of claim 6 , wherein the maintaining further includes defining first projections for the bucket identifiers as one or more of: a database, a database schema, a predefined set of the datasets, and a single one of the datasets. 8. The method of claim 7 , wherein the defining further includes defining second projections for the storage object identifiers as one or more of: the tables, the views, a subset of the tables, and a subset of the views. 9. The method of claim 1 , wherein the processing further includes using results returned from the processing to satisfy the object storage request. 10. The method of claim 9 , wherein the using further includes retaining at least some of the database statements to reproduce the results as a materialized view to satisfy the object storage request when presented a second time. 11. A method comprising: connecting an Application Programming Interface (API) service to an object storage application; projecting object storage formatted data into relational database formatted data; transforming an object storage request received from the object storage application for the object storage formatted data into one or more second equivalent database statements directed to the relational database formatted data, wherein the transforming comprises mapping the object storage formatted data to the relational database formatted data, the mapping translates the object storage request into the database statements that identify a bucket in the object storage request as a virtual bucket that includes a collection of one or more datasets in a relational database management system (DBMS) comprising one or more tables and views, and that identify an object in the object storage request as a virtual object that references a subset of the datasets included in the relational DBMS comprising one or more rows that belong to the tables and views; processing the one or more second equivalent requests against the relational database formatted data within the relational DBMS to generate relational database formatted results; and returning the virtual bucket having the virtual object in the relational database formatted results back to the API service based on the processing as the bucket and the object in object storage formatted results for delivery to the object storage application. 12. The method of claim 11 , wherein the projecting further includes maintaining relational database statements that when processed by the relational DBMS dynamically produces a projection of the relational database formatted data as one of more of the tables, the views, or a materialized view. 13. The method of claim 11 , wherein the projecting further includes mapping object identifiers provided in the object storage formatted data to the datasets. 14. The method of claim 13 , wherein the mapping further includes maintaining mappings for the object identifiers to reproduce the datasets when subsequent requests are made for the object storage formatted data. 15. The method of claim 14 , wherein the maintaining further includes leaving source tables associated with the datasets unchanged and retaining just the mappings to reproduce the datasets dynamically as needed. 16. The method of claim 11 , wherein the returning further includes hiding the relational database formatted results from the API service. 17. The method of claim 11 , further comprising load balancing and managing multiple different instances of the API service that provide object storage interfaces to applications when accessing the relational DBMS. 18. A system, comprising: a database management system; at least one hardware processor; a non-transitory computer-readable storage medium having executable instructions representing an object storage and database storage integrator; the object storage and database storage integrator configured to execute on the at least one hardware processor from the non-transitory computer-readable storage medium and to perform processing to: project object storage formatted data into database formatted data; transform object storage requests into database statements against the database formatted data, wherein the transform maps the object storage formatted data to the database formatted data, the map translates the object storage request into the database statements that identify a bucket in the object storage requests as a virtual bucket that includes a collection of one or more datasets in the database management system comprising one or more tables and views, and that identify an object in the object storage requests as a virtual object that references a subset of the datasets in the database management system comprising one or more rows that belong to the tables and views; process the database statements against the database formatted data using the database management system to generate database formatted results; and provide the database formatted results comprising the virtual bucket and the virtual object from the database statements back to requesting client applications as object storage formatted results comprising the bucket and the object. 19. The system of claim 18 , wherein the object storage and database storage integrator is further configured to perform processing to: maintain mappings be
Updating materialised views · CPC title
Presentation of query results · CPC title
Data format conversion from or to a database · CPC title
Interprogram communication · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.