Compare functions of different Virtual Storage products of EldoS
EldoS offers several products with different yet often confused functionality. The comparison chart is aimed at helping the developers choose the product that fits their needs most of all.
|Solid File System™ Application Edition||Solid File System OS Edition||Callback File System®||CallbackDisk™||CallbackFilter™|
|Platform support||Windows, Linux, FreeBSD, Android, MacOS X, iOS, custom||Windows, Linux, FreeBSD, MacOS X||Windows||Windows||Windows|
|Creates a virtual disk (drive letter or mounting point) in the system|
|Creates virtual files on existing "real" disks|
|Provides own file system|
|Includes built-in storage for the data|
|Lets you store the virtual disk in a single file on the disk||1|
|Lets you store the virtual disk in custom location (database, memory etc.)||1|
|Lets you store individual files in custom location (database, memory etc.)|
|Lets you control file and directory operations on the disk||2|
|Lets you control access to the disk on per-application basis|
|Includes built-in encryption for the data|
|Lets you plug custom encryption for the virtual disk in whole|
|Lets you plug custom encryption for individual files|
1 Callback File System (CBFS) doesn't have built-in storage for files. Your code can store files anywhere and in any format. One of possible options is to use Solid File System Application Edition as a file container for CBFS needs.
2 You can use SolFS OS Edition together with CallbackFilter to catch file operations performed on files in SolFS storage by third-party applications.