Data Persistence and Synchronization
The Akula client-side persistence mechanism lets you store data on a client device that persists across executions of the app. That means you can run the app and store information to the persistent data store. When you next run the app, that persistent data is available to be loaded back into the client app. The Akula client-side persistence mechanism supports CRUD (Create, Read, Update, Delete) operations on the persistent data store.
The Akula data synchronization mechanism is built on top of the persistent data store. With data synchronization, you can write data to the persistent data store, modify the data, and then upload those changes to the Akula Server. The server then updates the back end data store with all of your changes. If any other client has modified the data, the server returns those changes back to the client.
If you want to secure and protect your enterprise data when it is on a mobile device, you can encrypt the persistent data store. Encryption prevents unauthorized users from reading your data.
This section describes how to use the persistence and synchronization mechanisms in a client app, and includes the following sections:
- Modelling Data for Persistence
- Storing Persistent Data on the Client
- Synchronizing Client Data with the Akula Server
- Encrypting Data in the Persistent Data Store
- Clearing Persistent Data Stores
Sample client apps
Akula ships with sample client apps, including encryption and sync apps. For more information, see Samples.