From a90b04ccebc7a67f1cdb71c82a05ee1654c8a977 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Tue, 29 Dec 2020 02:44:47 -0800 Subject: [PATCH] Updated Filer as a Key Large Value Store (markdown) --- Filer-as-a-Key-Large-Value-Store.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Filer-as-a-Key-Large-Value-Store.md b/Filer-as-a-Key-Large-Value-Store.md index 641cdb1..3249605 100644 --- a/Filer-as-a-Key-Large-Value-Store.md +++ b/Filer-as-a-Key-Large-Value-Store.md @@ -4,7 +4,7 @@ Usually key-value stores are limited by the storage capacity. As the data size g Instead, we can move the large value data outside of KV stores, and only store the reference in KV stores. -With SeaweedFS, the value can be stored as a chunk on volume servers and can be referenced by chunk id, which is a small string. So you can get a key value store with almost unlimited size, while still have the same access speed for small values and reasonable speed for larger values. +With SeaweedFS, the large value can be stored as a chunk on volume servers and can be referenced by chunk id, which is a small string. In addition, the smaller values can be stored directly in KV stores, saving one network hop. So you can get a key value store with almost unlimited size, while still have the same access speed for small values and reasonable speed for larger values. ## How to do it?