From c21124b02ed124057708de4ce0a9ed3bfb284c11 Mon Sep 17 00:00:00 2001 From: Quentin Dufour Date: Tue, 13 Oct 2020 12:16:02 +0200 Subject: Fix Garage page --- "src/Technique/D\303\251veloppement/Garage.md" | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'src') diff --git "a/src/Technique/D\303\251veloppement/Garage.md" "b/src/Technique/D\303\251veloppement/Garage.md" index 6297ad3..49bd4c6 100644 --- "a/src/Technique/D\303\251veloppement/Garage.md" +++ "b/src/Technique/D\303\251veloppement/Garage.md" @@ -39,6 +39,11 @@ Swift and Pithos are probably the most similar to AWS S3 with their consistent h There was many attempts in research too. I am only thinking to [LBFS](https://pdos.csail.mit.edu/papers/lbfs:sosp01/lbfs.pdf) that was used as a basis for Seafile. +---- + +## Random notes + + - Cassandra (ScyllaDB) for metadata - Own system using consistent hashing for data chunks @@ -59,7 +64,7 @@ _Remark 1_ I really like the Rabin fingerprinting approach however deduplication _Remark 2_ Seafile idea has been stolen from this article: https://pdos.csail.mit.edu/papers/lbfs:sosp01/lbfs.pdf -#### Random notes + --> we should not talk about block. It is the abstraction that manipulate your FS to interact with your hard drive. "Chunk" is probably more appropriate. Block storage are a class of distributed storage where you expose the abstraction of your hard drive over the network, mainly SATA over ethernet, thinking to SCSI, FiberChannel, and so on -- cgit v1.2.3