TASK: add disambiguration between Cloud Storage and Tiered Storage

Sebastian Kurfürst 2021-12-24 08:19:03 +01:00
parent 779ecf7805
commit aea783be19

@ -1,4 +1,20 @@
## Motivation
> NOTE: SeaweedFS provides **two mechanisms** to use cloud storage:
> 1) [SeaweedFS Cloud Drive](https://github.com/chrislusf/seaweedfs/wiki/Cloud-Drive-Benefits)
> - in this case, you can **mount** an S3 bucket to the Seaweedfs file system (in the filer), and access the remote files
> through SeaweedFS. Effectively, SeaweedFS caches the files from the cloud storage.
> - In this mode, the file structure in cloud store is exactly matching the SeaweedFS structure - so every
> file in SeaweedFS will also become a file in the cloud storage provider.
> - This is useful in case you want to use the files inside the cloud provider's infrastructure.
> - However, this does **not support file encryption** in any way (obviously), as the files are put to Cloud Storage as is.
> 2) **Tiered Storage with Cloud Tier** (**<== You are here**)
> - In this mode, seaweedFS **moves full volume files to the cloud storage provider**, so files which are 1 GB (in our case) big.
> - This mode supports [Filer Data Encryption](https://github.com/chrislusf/seaweedfs/wiki/Filer-Data-Encryption) transparently.
> - The chunk files uploaded to the cloud provider are not usable outside of SeaweedFS.
Cloud storage is an ideal place to backup warm data. Its storage is scalable, and cost is usually low compared to on-premise storage servers. Uploading to the cloud is usually free. However, usually the cloud storage access is not free and slow.
SeaweedFS is fast. However, its capacity is limited by available number of volume servers.