From 2bc8f42a8483ae1eca186b4187367fd082bfc3bc Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Thu, 19 Aug 2021 12:32:14 -0700 Subject: [PATCH] Updated Cloud Cache Benefits (markdown) --- Cloud-Cache-Benefits.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Cloud-Cache-Benefits.md b/Cloud-Cache-Benefits.md index eba1398..fca2b08 100644 --- a/Cloud-Cache-Benefits.md +++ b/Cloud-Cache-Benefits.md @@ -53,7 +53,8 @@ However, how to make SeaweedFS work with data already on cloud? * It is not a proxy. Proxy is not ideal for low-latency read or write operations. * Its cache size is not limited. With unlimited size, all file content can be localized. So the read can be fast even on the first attempt, without worrying cached items are evicted due to capacity. -* Its cache is not write-through. +* Its cache is not write-through. Local changes are asynchronously write back to the cloud within seconds. +* It does not change file storage layout in the cloud storage. Other tools can access the files on the cloud storage as usual. * It does not need to link to the original data source. After caching all the file content, you can choose to detach from the remote storage. # Why SeaweedFS Cloud Cache?