Data Caching

Data caching is initial loading (or filling) the cache database (CDB, or Unwired Server cache) with enterprise information system (EIS) data, then continuing to refresh the CDB with changes from the EIS or mobile device on an ongoing basis.

Since continual synchronization of the data between the EIS and device puts a load on the EIS, Unwired Platform provides several options for loading and refreshing the data cache.

Options include narrowing the EIS data search so that only specific data is retrieved, identifying effective policies for handling data updates once operations are performed, scheduling periodic updates to occur when system usage is low, updating only changed data in the CDB, and so forth.

You can use multiple options to load and refresh the right data at the right time, and to deliver the smallest, most focused payload to the mobile device.

The primary loading schemes provide a trade-off between time and storage space. For example, bulk loading takes more time because data is loaded for all users, but once loaded, the data can be shared between users.

Bulk loading – data for all users is loaded in bulk.
Partitioning data loading – only user relevant data, or partition, is loaded.
On-demand loading – data is not filled, until the client performs synchronization.
Scheduled loading – data is filled periodically according to a schedule you set.

Data change notification (DCN) facilitates propagation of data changes from the back-end enterprise information system (EIS) to the Unwired Server or HTTP/HTTPS interface for any MBO. The DCN payload containing changed data is applied to the cache and the change gets published to subscribing device users based on a change detection interval time. DCN is used for cases where the cache refresh may be expensive due to volume. This option is the least intrusive and most optimal for addressing high-load environments and optimizing the load on the EIS data sources to keep the Unwired Server cache consistent.