Each store singleton is configured with a set of configuration parameters common across all data that comes to the store. Each singleton is expected to handle output to multiple containers, with routing of data to container managed by the naming of sets.
Each store plugin provides its own concept of what a container means. The container may be mapped to a file, a directory hierarchy, a database, or anything else the author chooses. The plugin may apply numerical transformations before storage.
Lifecycle and functions: