Simple pricing.
Distributing data across tens of thousands of underutilized storage nodes costs less and eliminates the need for multi-region replication.
No, Object Mount does not compress or deduplicate data. This is an explicit design goal. Scrambling data–which is needed for compression/dedupe or requiring an S3-to-S3 gateway to translate between scrambled and unscrambled formats–produces unacceptably low performance and scalability. Instead, Storj maps files to objects in a 1-to-1 fashion that is both POSIX compatible and directly accessible on the S3 interface, delivering ultra-high performance.
No, the Object Mount command merely enables its direct mode to intercept the user’s preferred shell, whether that is bash, zsh, csh, or something else. Tab completion and other actions are due to the support within the existing shell, rather than because of Object Mount doing something. Running commands like ls actually launches the unmodified ls binary installed on the system.
Yes, Object Mount is designed to work with any software, including software that Storj customers have written. Note that some applications may parse URIs and treat them separately. In those cases, Storj recommends the use of path-style access. Alternatively, add the application to the uricompat option in Object Mount direct mode to intercept command line URI arguments.
Yes, Object Mount supports Windows, Mac, and Linux.
Yes, Object Mount can be used with containers in multiple ways:
(i) by mounting on the host and bind-mounting into the container,
(ii) by injecting the Object Mount library into an unmodified container Storj provides a seamless way to do this),
(iii) or by installing Object Mount inside the container.
For instructions specific to Docker and Singularity, please see the user guide. The CSI driver for Kubernetes is now available on request. Note that Object Mount does not require any special privileges to run inside a container.