Synchronizing Client Data with the Akula Server
An Akula client app can write data locally to a persistent data store, and then read that data back some time later. The data persists across executions of the app so that you can also read that data back after stopping and then restarting the app. For more information, see Storing Persistent Data on the Client.
The Akula data synchronization mechanism is built on top of the persistent data store. The persistence manager keeps track of all changes made to the local data, such as adds, deletes, and updates. The synchronization manager can upload those changes to an app scope running on the Akula Server. The app scope then updates the back end data store with all of the changes from the client. Also, if the back end data store has been modified since the last time the client downloaded data, the app scope returns those changes to the client.