From 779ecf78053cc056daeaf2c8d89f5282b3dd9404 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Kurf=C3=BCrst?= Date: Fri, 24 Dec 2021 08:17:34 +0100 Subject: [PATCH] TASK: add disambiguration between Cloud Storage and Tiered Storage --- Cloud-Drive-Benefits.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/Cloud-Drive-Benefits.md b/Cloud-Drive-Benefits.md index 2cf1705..4475b70 100644 --- a/Cloud-Drive-Benefits.md +++ b/Cloud-Drive-Benefits.md @@ -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: