Virtual persistence

US9507607B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9507607-B2
Application numberUS-201313891549-A
CountryUS
Kind codeB2
Filing dateMay 10, 2013
Priority dateMay 10, 2013
Publication dateNov 29, 2016
Grant dateNov 29, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A virtual persistence platform is described that provides requirement-driven persistence store orchestration. Application developers can annotate program code with persistence properties and requirements, and a compiler component of the virtual persistence platform generates a persistence service level agreement (PSLA) that becomes attached to the application. After deployment and launch, the virtual persistence platform uses the PSLA to handle persistence commands from the application and perform persistence store orchestration.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for providing a persistence layer to an application, the method comprising: receiving, from the application, an entity-level persistence command for an entity of the application, the entity comprising an object of the application that can be persisted; retrieving metadata associated with the entity, wherein the metadata specifies a set of persistence requirements associated with the entity, a virtual instruction set, and an entry point to a virtual instruction in the virtual instruction set associated with the received entity-level persistence command, the persistence requirements including a volume of processed data, a partition tolerance, or a latency; selecting a database system from a plurality of candidate database systems based on the set of persistence requirements associated with the entity and persistence capabilities associated with the candidate database systems; linking the virtual instruction to an instruction processor specific to the selected database system; and executing the received entity-level persistence command by invoking the linked instruction processor to translate the virtual instruction to one or more database-specific commands and apply the one or more database-specific commands to the selected database system. 2. The method of claim 1 , wherein the set of persistence requirements associated with the entity of the application is generated by: parsing annotations within program code for the application to extract one or more persistence properties; and generating a persistence service level agreement (PSLA) using an automata based on the extracted persistence properties, the PSLA specifying the set of persistence requirements associated with the entity of the application. 3. The method of claim 1 , wherein the set of persistence requirements associated with the entity of the application is generated by: determining one or more persistence properties based on a class interface within program code for the entity of the application; and generating a persistence service level agreement (PSLA) using an automata based on the determined persistence properties, the PSLA specifying the set of persistence requirements associated with the entity of the application. 4. The method of claim 1 , wherein the persistence capabilities associated with the candidate persistence stores are registered in a metadata registry. 5. The method of claim 1 , wherein the entity-level persistence command includes a data retrieval command for a query defined over the entity of the application. 6. The method of claim 5 , wherein: the set of persistence requirements associated with entity for the application conflict with a set of persistence requirements associated with the query defined over the entity; and retrieved metadata for the query includes an ordered virtual instruction chain comprising a system-generated delta query, an Extract-Transform-Load virtual instruction, and a system-generated replica entity. 7. The method of claim 1 , further comprising: decomposing the entity for the application into a first child entity having a first set of persistence requirements and a second child entity having a second set of persistence requirements, wherein the first and second sets of persistence requirements are different; selecting a first persistence store for the first child entity based on the first set of persistence requirements; selecting a second persistence store for the second child entity based on the second set of persistence requirements; and executing the received entity-level persistence command using linked instruction processors specific to each of the first and second persistence stores. 8. The method of claim 1 , wherein the candidate database systems comprises two of more of a relational database system, a non-relational big-table distributed database system, a document-oriented database system, a key-value database system, and a graph database system. 9. A method for providing a persistence layer to an application, the method comprising: receiving a command to register an entity of the application; retrieving metadata associated with the entity and metadata associated with a query linked to the entity, wherein the metadata associated with the query includes an Extract-Transform-Load (ETL) virtual instruction associated with the received register command; selecting a first persistence store for persisting the registered entity based on a set of persistence requirements associated with the entity; selecting a second persistence store for executing the query based on a set of persistence requirements associated with the query; launching an ETL instruction processor based on the ETL virtual instruction to extract, transform, and load entity data from the first persistence store to the second persistence store; receiving, from the application, a data retrieval command for the query defined over the entity; retrieving the metadata associated with the query, wherein the metadata specifies the set of persistence requirements associated with the query and an entry point to a virtual instruction associated with the received data retrieval command; selecting a persistence store from a plurality of candidate persistence stores based on the set of persistence requirements associated with the query; linking the virtual instruction to an instruction processor specific to the selected persistence store; and executing the received data retrieval command using the linked instruction processor specific to the selected persistence store. 10. A non-transitory computer readable storage medium having stored thereon program instructions for providing a persistence layer to an application, wherein execution of the program instructions by one or more processes of a computer system causes the one or more processors to carry out the steps of: receiving, from an application, an entity-level persistence command for an entity of the application, the entity comprising an object of the application that can be persisted; retrieving metadata associated with the entity, wherein the metadata specifies a set of persistence requirements associated with the entity, a virtual instruction set, and an entry point to a virtual instruction in the virtual instruction set associated with the received entity-level persistence command, the persistence requirement including a volume of processed data, a partition tolerance, or a latency; selecting a database system from a plurality of candidate database systems based on the set of persistence requirements associated with the entity and persistence capabilities associated with the candidate database systems; linking the virtual instruction to an instruction processor specific to the selected database system; and executing the received entity-level persistence command by invoking the linked instruction processor to translate the virtual instruction to one or more database-specific commands and apply the one or more database-specific commands to the selected database system. 11. The non-transitory computer readable storage medium of claim 10 , wherein the set of persistence requirements associated with the entity of the application is generated by: parsing annotations within program code for the application to extract one or more persistence properties; and generating a persistence service level agreement (PSLA) using an automata based on the extracted persistence properties, the PSLA specifying the set of persistence requirements associated with the entity of the application. 12. The non-transitory computer readable storage medium of claim 10 , wherein the set of persistence requirements associat

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9507607B2 cover?
A virtual persistence platform is described that provides requirement-driven persistence store orchestration. Application developers can annotate program code with persistence properties and requirements, and a compiler component of the virtual persistence platform generates a persistence service level agreement (PSLA) that becomes attached to the application. After deployment and launch, the v…
Who is the assignee on this patent?
Vmware Inc
What technology area does this patent fall under?
Primary CPC classification G06F9/4435. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 29 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).