Data storage APIs

There are several ways you can store, share, and manage data for your apps:

• File system: Store data in files and folders using the FileConnection API
• SQLite database: Store data in relational databases using the Database API
• Persistent store: Save objects across smartphone restarts using the PersistentStore API
• Runtime store: Save objects nonpersistently, which is useful for sharing data between applications and creating system-wide singletons, using the RuntimeStore API
• Record store: Store data in the MIDP Record Management System using the RMS API

The following table compares the features of each approach:

Following are some considerations for choosing a data storage approach:

• The file system and SQLite databases are typically the most efficient storage location for large, read-only files such as videos or large graphics.
• Memory on wireless smartphones can be very limited, so you should consider not storing all data on the smartphone. BlackBerry smartphones are frequently connected so your application can access data when needed. In many cases, the best approach is to store data across smartphone restarts only for data that is frequently accessed.
• When you consider where to store essential data, keep in mind that microSD cards can be removed.
• There is more latency in writing to application storage than there is in reading from it. For example, reading from the persistent store is relatively fast while commits are relatively slow.
• The file system and record store are standards-based approaches, while the persistent store and runtime store are specific to BlackBerry smartphones. If you want your application to run on other Java ME compatible devices, you should consider a standards-based approach.