Abstract: Guaranteed message sequencing between a first and second database is described. An example method includes maintaining first state information associated with the first database at the first database, where second state information associated with the first database is maintained at the second database. The client sends, to the second database, a message describing changed rows between the first database and the second database since a last synchronization and the first state information. The client subsequently receives, from the second database, status of the last synchronization, where the status is determined by the second database based on the first state information and the second state information.

Abstract: In an example embodiment, one or more pages from a database are stored in a page cache stored in a shared memory, the one or more pages stored in a packed format. One or more rows from the database are stored in a row cache stored in the shared memory, the one or more rows stored in an unpacked format. A request for a row of the database is received. Then, the row cache is searched for the row. In response to a determination that the row cannot be found in the row cache, the page cache is searched for the row. Finally, the row is returned.

Abstract: A method for providing mapping between a first data model and a second data model may include sending a request for metadata to a data producer providing data using the second data model. The metadata may be received from the data producer and analyzed to determine a structure of the second data model. System tables may be created based on the analysis of the metadata. The system tables may include data tables to store data from the data producer and to provide the mapping between the metadata of the second data model and the data tables in the first data model. Requests may be made to the data producer for data to be retrieved and populated in the data tables using the first data model.

Abstract: A method for processing data requests may include storing data on a client device received from a data provider maintaining the data. A request may be received to modify the data maintained by the data provider. After connectivity to the data provider is available, the request may be sent to the data provider. After connectivity is not available the request may be processed based on the data stored on the client device and the modified data may be stored on the client device.

Abstract: In an example embodiment, one or more pages from a database are stored in a page cache stored in a shared memory, the one or more pages stored in a packed format. One or more rows from the database are stored in a row cache stored in the shared memory, the one or more rows stored in an unpacked format. A request for a row of the database is received. Then, the row cache is searched for the row. In response to a determination that the row cannot be found in the row cache, the page cache is searched for the row. Finally, the row is returned.

Abstract: A method for processing data requests may include storing data on a client device received from a data provider maintaining the data. A request may be received to modify the data maintained by the data provider. After connectivity to the data provider is available, the request may be sent to the data provider. After connectivity is not available the request may be processed based on the data stored on the client device and the modified data may be stored on the client device.

Abstract: Guaranteed message sequencing between a first and second database is described. An example method includes maintaining first state information associated with the first database at the first database, where second state information associated with the first database is maintained at the second database. The client sends, to the second database, a message describing changed rows between the first database and the second database since a last synchronization and the first state information. The client subsequently receives, from the second database, status of the last synchronization, where the status is determined by the second database based on the first state information and the second state information.

Abstract: A method for providing mapping between a first data model and a second data model may include sending a request for metadata to a data producer providing data using the second data model. The metadata may be received from the data producer and analyzed to determine a structure of the second data model. System tables may be created based on the analysis of the metadata. The system tables may include data tables to store data from the data producer and to provide the mapping between the metadata of the second data model and the data tables in the first data model. Requests may be made to the data producer for data to be retrieved and populated in the data tables using the first data model.

Abstract: A server system may include a request handler and a database generator. The request handler may receive at least one request from a mobile client device on a user side or from a source server. If the request handler determines that the at least one request requires an initialization of a first mobile database in the mobile client device on the user, the database generator may generate a second mobile database in the server system populated with corresponding requested data from the source server, and the request handler may transmit the second mobile database with the corresponding requested data as a file to the mobile client device. The file of the second mobile database may be stored on the mobile client device as the first mobile database.