SQLite
For development and testing on a single-host ScaleOut cluster, a SQLite persistence connection can be used to connect your ScaleOut Active Caching module to a SQLite database file. This allows modules to persist modifications to a SQLite database file and retrieve saved values when the module first creates an object.
To connect to a SQLite database, supply a SQL database connection string. This string is an expression that contains the parameters required for applications to connect to a database server. Connection strings typically include the path to the SQLite database file. (Note that the directory containing the database file must already exist; the connection will not create it.)
Here is a screenshot of the dialog in the ScaleOut Active Caching UI for creating a SQLite connection:

The “Create table if missing” option causes the connection to automatically create the table used to store instance data if it does not already exist in the database. The table will be named ScaleoutModuleInstances.
Enable SQLite Persistence for a Module
When launching your module package through the ScaleOut Active Caching UI, you can enable persistence on a module-by-module basis by selecting the SQLite persistence provider defined above.
If write-through is enabled, instances in your module will automatically persist their state to SQLite every five seconds if their state has been modified.
If read-through is enabled, instances will retrieve their persisted state from SQLite when they are first created.
