aboutsummaryrefslogtreecommitdiff
path: root/src/Technique/Développement/Garage.md
diff options
context:
space:
mode:
Diffstat (limited to 'src/Technique/Développement/Garage.md')
-rw-r--r--src/Technique/Développement/Garage.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/src/Technique/Développement/Garage.md b/src/Technique/Développement/Garage.md
index 6297ad3..49bd4c6 100644
--- a/src/Technique/Développement/Garage.md
+++ b/src/Technique/Développement/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