21–30 of 120 posts
Interesting, I’d guess list operations are significantly faster because of the cache, even a hash map like Redis? That can be a real slowdown in s3 with large quantities of files.
I am also not sure how it is a "distributed" file system given its storage is entirely done by S3. Should I call my backup program that backups my data to S3 every night a "distributed system"? When running on top of Redis, it explicitly mentions that Redis cluster is not supported. I haven't used Redis for many years, did I miss something here? A "distributed" file system built on top of a single instance of Redis? Sounds not very "distributed" to me.
Does it pass the generic xfstests?
This is pretty cool. How does the storage format work? Would I be able to download storage chunks from s3 and somehow recover my files from chunks?
We will provide tools to dump the metadata as JSON, then you could recover your files using that.
How does this compare with seaweedfs? That also has fuse and can store metadata and small data in redis and provides its own s3 api, so there's one less moving part.
The core of seaweedfs is to manage many small blobs, you can use SeaweedFS together with JuiceFS to have a full featured POSIX file system.
I advocate for using Route 53 as a database and even I think this is terrifying.
Although the repo looks new, the founder said they've been building it for 4 years. https://news.ycombinator.com/item?id=25724925
I advocate for using Route 53 as a database and even I think this is terrifying.
Out of curiosity how do you use a DNS service as a database?