Live data from Hacker News

A distributed Posix file system built on top of Redis and S3

github.com

11–20 of 120 posts

Re: A distributed Posix file system built on top of Redis and S3

#11
post #10

Would not an NFS solution have this kind of caching and durability built-in? Without doing actual “Jepsen tests” (they are almost a generic term at this point due to their name) how would this improve my life versus buying an NFS vendor solution, or rolling my own?

NFS doesn’t scale to effectively infinity with an underlying object store. This is to give you a ton of storage without using a traditional volume target with your app that, for whatever reason, requires a posix filesystem.

I’m sure someone from AWS can’t comment, but I imagine this is how AWS’ EFS service is built (NFS wire protocol to clients, but using S3 and metadata caching under the hood). Blobs or blocks doesn’t matter much, just how fast the abstraction is.

Re: A distributed Posix file system built on top of Redis and S3

#13

I advocate for using Route 53 as a database and even I think this is terrifying.

I mean, kinda same, because my lizard brain still remembers getting burned - but in theory it's not much different than what Storage Gateway in File Gateway mode or Nasuni and others have been doing for years, is it?

Re: A distributed Posix file system built on top of Redis and S3

#20

Although the repo looks new, the founder said they've been building it for 4 years. https://news.ycombinator.com/item?id=25724925

Our team is JuiceFS's launching customer. We've been using its enterprise offering since late 2016 and accumulated several hundreds TBs of data on JuiceFS along the way, it worked well.

I've wrote a blog post (in Chinese) explaining our MySQL backup practice around JuiceFS in 2018. https://tech.xiachufang.xyz/2018-04-17/mysql-backup-practice

They provided an open source version recently.

Post reply on HN