mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
TASK: add disambiguration between Cloud Storage and Tiered Storage
parent
d4650c42f9
commit
779ecf7805
|
@ -1,5 +1,19 @@
|
|||
# Introduction
|
||||
|
||||
> NOTE: SeaweedFS provides **two mechanisms** to use cloud storage:
|
||||
> 1) **SeaweedFS Cloud Drive** (**<== You are here**)
|
||||
> - 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](https://github.com/chrislusf/seaweedfs/wiki/Cloud-Tier)
|
||||
> - 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 is not for everyone
|
||||
Nowadays, the industrial trend is to go to cloud storage, since "everybody is doing it". But after really using cloud storage, many users will find out:
|
||||
|
||||
|
|
Loading…
Reference in a new issue