Dynamic storage backend

[meatballs]

At present, the library assumes, and hard codes, a data tables storage backend with a db schema where an attribute maps directly to a column.

Instead, this should be injected dynamically into the class with some common options available within the library (eg datatables but with a single simple object column for the entire instance).