The SwiftStack Gateway was designed to provide bi-modal (i.e. filesystem and object API) access to data stored in SwiftStack, in order to help applications which might not support the Swift or S3 API today start using SwiftStack storage via SMB or NFS. However, in order to provide bi-modal access, the Gateway is not appropriate for all applications or use cases that require SMB or NFS.
Good use cases for the Gateway include:
- Applications which archive data to SMB/NFS (with little to no read-back) which will be later adapted to use Swift/S3
- Applications which archive data to SMB/NFS (with little to no read-back) which will be later replaced to use Swift/S3 natively
If your application doesn't and won't ever require object API access to data stored via SMB/NFS, you should consider other Gateway solutions (such as Avere or SoftNAS) which can provide good SMB/NFS access to SwiftStack without offering object API access to your data.
The gateway should not be used for the following uses:
- Backing storage for active databases
- Hosting virtual machine disk images
- Home directories
- Applications requiring high I/O
- Applications which store a large number of files (hundreds of thousands) in a single directory