mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2024-01-19 02:48:24 +00:00
Updated Cloud Cache Benefits (markdown)
parent
0e27e628eb
commit
7d177f1a31
|
@ -68,15 +68,18 @@ However, how to make SeaweedFS work with data already on cloud?
|
|||
* Users can also choose to never uncache, basically treating cloud copy as a backup.
|
||||
* Big Data
|
||||
* Problem
|
||||
* Run MapReduce, Spark, and Flink jobs on mounted folders for faster computation.
|
||||
* Run MapReduce, Spark, and Flink jobs on cloud data is slow due to metadata operations.
|
||||
* Repeated data access increases unnecessary cost.
|
||||
* May need to work with the cloud ecosystem.
|
||||
* With SeaweedFS Cloud Cache
|
||||
* Avoiding slow cloud storage metadata access.
|
||||
* Large amount of data access will not increase cost.
|
||||
* Access data only once.
|
||||
* Write back data to work with cloud ecosystems.
|
||||
* Cloud Storage Vendor Agnostic
|
||||
* Problem
|
||||
* Different datasets may need to be on different vendors, based on access pattern, latency, cost, etc.
|
||||
* Transparently switch to from one vendor to another.
|
||||
* Different datasets may need to be on different vendors, based on access pattern, latency, cost, etc.
|
||||
* With SeaweedFS Cloud Cache
|
||||
* Transparently switch to from one vendor to another.
|
||||
* Move Off Cloud
|
||||
* Problem
|
||||
* Cloud storage is costly!
|
||||
|
|
Loading…
Reference in a new issue