aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lu <chrislusf@users.noreply.github.com>2020-01-01 12:01:27 -0800
committerGitHub <noreply@github.com>2020-01-01 12:01:27 -0800
commit5927f4f1b7cead64091104b144ce11532c13453e (patch)
tree6d09fd2c512df7a0ead83d2e1d5267b2c0288fc5
parent50d44480e7b77e87f676afb596e67ce3ee3fc74f (diff)
downloadseaweedfs-5927f4f1b7cead64091104b144ce11532c13453e.tar.xz
seaweedfs-5927f4f1b7cead64091104b144ce11532c13453e.zip
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index b5f78da7c..39494325a 100644
--- a/README.md
+++ b/README.md
@@ -83,7 +83,7 @@ SeaweedFS is a simple and highly scalable distributed file system. There are two
SeaweedFS started as an Object Store to handle small files efficiently. Instead of managing all file metadata in a central master, the central master only manages file volumes, and it lets these volume servers manage files and their metadata. This relieves concurrency pressure from the central master and spreads file metadata into volume servers, allowing faster file access (O(1), usually just one disk read operation).
-SeaweedFS can be tiered to the cloud. With hot data on local cluster, and warm data on the cloud with O(1) access time, SeaweedFS can transparently achieve both fast local access time and elastic cloud storage capacity.
+SeaweedFS can transparently integrate with the cloud. With hot data on local cluster, and warm data on the cloud with O(1) access time, SeaweedFS can achieve both fast local access time and elastic cloud storage capacity, without any client side changes.
There is only 40 bytes of disk storage overhead for each file's metadata. It is so simple with O(1) disk reads that you are welcome to challenge the performance with your actual use cases.