Configurable development platform integrating heterogeneous persistence systems

1. A system for integrating an application with a plurality of persistence systems, comprising:

a processor; and

a memory comprising instructions configured to cause the processor to:

receive, from a browser of a client, a request for access to the application, the application developed for a first persistent system, the application operational on a platform, the platform providing functionality of the application to allow the application to access and operate against information on the first persistent system and simultaneously access and operate against information on a heterogeneous second persistent system;

in response to receiving the request for access to the application, provide, to the client, instructions that when implemented cause a user interface to be dynamically generated in the browser of the client, the user interface for using the application;

provide a data model to translate input from and output to the user interface for use by the application, the data model comprising a set of entity classes mapping to different objects, entities, or tables in different persistent systems allowing use of the application in different persistent systems by selecting an entity class that maps to an object, entity, or table in a specific persistent system;

instantiate an entity class for the data model;

determine, using the entity class, a manager, the manager executing operations including validating and processing the request;

process the request using the manager to generate a native request that is executable by the second persistent system; and

send the native request to allow the application to execute on the second persistent system.

2. The system of claim 1 , wherein the first persistent system is an enterprise database and the application is an on-premises third-party application.

3. The system of claim 1 , wherein the second persistent system is a cloud-based system and the application is a cloud-based third-party application.

4. The system of claim 1 , wherein providing the data model comprises defining the entity class and providing a first mapping to an object of the first persistence system and a second mapping to an object of the second persistence system.

5. The system of claim 1 , wherein the processor is further configured to receive a request from the user interface to perform a persistence operation against an object of the first persistence system and an object of the second persistent system.

6. The system of claim 5 , wherein the persistence operation is one from the group of create, read, update, delete, bulk save, and bulk delete.

7. The system of claim 4 wherein the processor is further configured to associate the entity class with a query and the query is declarative.

8. The system of claim 7 , wherein the query adheres to an agnostic schema of the first or the second persistent system.

9. The system of claim 1 , wherein the data model includes an agnostic schema for the first or the second persistent system.

10. A computer-implemented method for integrating an application with a plurality of persistence systems, comprising:

receiving, from a browser of a client, a request for access to the application, the application developed for a first persistent system, the application operational on a platform, the platform providing functionality of the application to allow the application to access and operate against information on the first persistent system and simultaneously access and operate against information on a heterogeneous second persistent system;

in response to receiving the request for access to the application, providing, to the client, instructions that when implemented cause a user interface to be dynamically generated in the browser of the client, the user interface for using the application;

providing a data model to translate input from and output to the user interface for use by the application, the data model comprising a set of entity classes mapping to different objects, entities, or tables in different persistent systems allowing use of the application in different persistent systems by selecting an entity class that maps to an object, entity, or table in a specific persistent system;

instantiating an entity class for the data model;

determining, using the entity class, a manager, the manager executing operations including validating and processing the request;

processing the request using the manager to generate a native request that is executable by the second persistent system; and

sending the native request to allow the application to execute on the second persistent system.

11. The method of claim 10 , wherein the first persistent system is an enterprise database and the application is an on-premises third-party application.

12. The method of claim 10 , wherein the second persistent system is a cloud-based system and the application is a cloud-based third-party application.

13. The method of claim 10 , wherein providing the data model comprises defining the entity class and providing a first mapping to an object of the first persistence system and a second mapping to an object of the second persistence system.

14. The method of claim 10 , further comprising receiving a request from the user interface to perform a persistence operation against an object of the first persistence system and an object of the second persistent system.

15. The method of claim 14 , wherein the persistence operation is one from the group of create, read, update, delete, bulk save, and bulk delete.

16. The method of claim 13 , further comprising associating the entity class with a query and the query is declarative.

17. The method of claim 16 , wherein the query adheres to an agnostic schema of the first or the second persistent system.

18. The method of claim 10 , wherein the data model includes an agnostic schema for the first or the second persistent system.