Enterprise resource planning running on multiple databases

1. A computer-implemented method comprising:

identifying a selection of data stored in a database to be used in conjunction with an in-memory database, the selection of data corresponding to an application;

receiving a selection of a storage mode corresponding to a dual system storage mode or a source system storage mode, the storage mode being selectable by a user input and, upon selection of the dual system storage mode, the application interacts with both the database and the in-memory database, and wherein upon selection of the source system storage mode, the application interacts with the database only;

replicating, by a replication server, the selection of data in the in-memory database; and

based on the dual system storage mode being selected:

generating an entry corresponding to the selection of data in a connection layer lookup table of a database connection layer;

in response to instructions from the replication server, switching off an application lookup table used by the application to find the selection of data in the database;

receiving a query from the application for a portion of the selection of data;

determining whether the connection layer lookup table includes an entry corresponding to the portion of the selection of data;

routing the query to the in-memory database based on the connection layer lookup table including an entry corresponding to the portion of the selection of data; and

routing the query to the database based on the connection layer lookup table not including an entry corresponding to the portion of the selection of data.

2. The computer-implemented method of claim 1 , further comprising:

accessing and updating data from the selection of data in the database; and

replicating, by the replication server, the updated data from the selection of data in the database to the in-memory database based on the source system storage mode being selected.

3. The computer-implemented method of claim 1 , further comprising verifying that the selection of data is the same in both the database and the in-memory database after the replicating.

4. The computer-implemented method of claim 1 , wherein the application is a business application and the database is a business application database.

5. The computer-implemented method of claim 1 , further comprising:

building a new application based on the selection of data in the in-memory database;

generating new data using the new application; and

storing the new data directly in the in-memory database without replicating the new data from the in-memory database back to the database.

6. A system comprising:

one or more hardware processors;

a storage device comprising a database;

an in-memory system comprising an in-memory database;

an application implemented by the one or more hardware processors and configured to:

identify a selection of data stored in the database to be used in conjunction with the in-memory database, the selection of data corresponding to the application,

receive a selection of a storage mode corresponding to a dual system storage mode or a source system storage mode, the storage mode being selectable by a user input and, upon selection of the dual system storage mode, the application interacts with both the database and the in-memory database, and wherein upon selection of the source storage system mode, the application interacts with the database only; and

a replication server configured to replicate the selection of data in the in-memory database;

the application being further configured to, based on the dual system storage mode being selected:

in response to instructions from the replication server, switching off an application lookup table used by the application to find the selection of data in the database;

receive a query from the application for a portion of the selection of data;

determine whether the connection layer lookup table includes an entry corresponding to the portion of the selection of data;

route the query to the in-memory database based on the connection layer lookup table including an entry corresponding to the portion of the selection of data; and

route the query to the database based on the connection layer lookup table not including an entry corresponding to the portion of the selection of data.

7. The system of claim 6 , wherein the replication server is configured to:

access and update data from the selection of data in the database; and

replicate the updated data from the selection of data in the database to the in-memory database based on the source system storage mode being selected.

8. The system of claim 6 , wherein the application is configured to verify that the selection of data is the same in both the database and the in-memory database after the replicating.

9. The system of claim 6 , wherein the application is a business application and the database is a business application database.

10. The system of claim 6 , wherein the application is further configured to build a new application based on the selection of data in the in-memory database, to generate new data using the new application, and to store the new data directly in the in-memory database without replicating the new data from the in-memory database back to the database.

11. A non-transitory machine-readable storage medium storing instructions which, when executed by at least one processor, performs operations comprising:

identifying a selection of data stored in a database to be used in conjunction with an in-memory database, the selection of data corresponding to an application;

receiving a selection of a storage mode corresponding to a dual system storage mode or a source system storage mode, the storage mode being selectable by a user input and, upon selection of the dual system storage mode, the application interacts with both the database and the in-memory database, and wherein upon selection of the source storage system mode, the application interacts with the database only; and

based on the dual system storage mode being selected:

replicating, by a replication server, the selection of data in the in-memory database;

generating an entry corresponding to the selection of data in a connection layer lookup table of a database connection layer;

in response to instructions from the replication server, switching off an application lookup table used by the application to find the selection of data in the database;

receiving a query from the application for a portion of the selection of data;

determining whether the connection layer lookup table includes an entry corresponding to the portion of the selection of data;

routing the query to the in-memory database based on the connection layer lookup table including an entry corresponding to the portion of the selection of data; and

routing the query to the database based on the connection layer lookup table not including an entry corresponding to the portion of the selection of data.

12. The non-transitory machine-readable storage medium of claim 11 , wherein the operations further comprise:

accessing and updating data from the selection of data in the database; and

replicating, by the replication server, the updated data from the selection of data in the database to the in-memory database based on the source system storage mode being selected.

13. The non-transitory machine-readable storage medium of claim 11 , wherein the operations further comprise verifying that the selection of data is the same in both the database and the in-memory database after the replicating.

14. The non-transitory machine-readable storage medium of claim 11 , wherein the application is a business application and the database is a business application database.

15. The non-transitory machine-readable storage medium of claim 11 , wherein the operations further comprise:

building a new application based on the selection of data in the in-memory database;

generating new data using the new application; and

storing the new data directly in the in-memory database without replicating the new data from the in-memory database back to the database.