When DreamFactory Enterprise™ provisions a new instance, a directory is created for it to use as local storage. The location of this directory depends on the mount assigned to the server on which the instance was provisioned.
Mounts can be local or remote storage. As long as the storage space is accessible via the file system of the server, it can be utilized for storage.By default, DreamFactory Enterprise™ defines the mount point
/data/storagefor your initial cluster. This directory contains a subdirectory for each cluster. The initial installation defaults to local as the storage area. This exists on your system in
/data/storage/local. When you create new clusters, you can configure their storage areas in a different subdirectory, or different mount point altogether. It is designed to be flexible and map to most storage scenarios.
Layout and Structure
Below is a diagram of the default layout for storage.
/datatree contains self-explanatory subdirectories. Under
/data/storageis where it begins to get interesting.
Lightweight StripingTo spread the storage load, as it were, of thousands of virtual instances, the instance storage tree implements a simplistic hashed directory tree. Each Dashboard user is assigned a unique storage ID in the form of a GUID (
[[DFE/Architecture/Database/User|User.storage_id_text]]). This GUID is hashed, and with it and the first four bytes are used to create a three-level nested subdirectory. Example: User id #1 has a storage ID of
00933DBC-C7A9-DE0E-5D38-FB23B574A580. Applying a SHA1 hash gives us