Mobile data requirements include identifying the data needed and when, how current it needs to be, and which of your users can access it.
These requirements help drive update, synchronization, and access decisions. For example, if data rarely changes, synchronization is required only occasionally; if data is very volatile, a comprehensive strategy is required to ensure data is kept current on the device.
If system processing load is a concern, reduce the frequency that data is updated or accessed in the consolidated database (cache), or filter out unneeded data using system features such as SQL data queries. For data that are only used on the device to persist data across application launches, local caching or temporary usage, a local MBO can be defined.