JuiceFS VS LakeFS

JuiceFS Reviews

LakeFS Reviews

JuiceFS mentions (4)

• SeaweedFS fast distributed storage system for blobs, objects, files and datalake

  The comments already mention several alternatives (Minio, Ceph, GarageFS). I think another one, not mentioned yet, is JuiceFS [1]. Found one comparison here [2]. [1] https://juicefs.com/en/ [2] https://dzone.com/articles/seaweedfs-vs-juicefs-in-design-and-features. - Source: Hacker News / 3 months ago

• An open-source distributed object storage service

  For this use-case, I like JuiceFS better. * https://juicefs.com/en/ * https://github.com/juicedata/juicefs I am not affiliated with them, just a regular user. - Source: Hacker News / over 1 year ago

• Use S3 as NFS for EC2

  EFS would be my first choice for a production service, but since you're experimenting, at a recent hackathon at $work a team got really good results from https://juicefs.com/en/ backed by S3, enough that it warrants further investigation. Source: over 1 year ago

• Extending NAS to S3 (Compatible Storage)

  Https://juicefs.com/ looks interesting. Object Storage -> POSIX. Source: almost 2 years ago

LakeFS mentions (6)

• Ask HN: AWS S3, Cloudflare R2, GCS, Wasabi, or B2?

  I would add https://github.com/gaul/s3proxy to your list. - Source: Hacker News / about 1 month ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  * data state - this is contents of both your data and metadata at a given point in time. if your data doesn't fit into a single database, this can be difficult to manage. We use this technology to help us: https://lakefs.io/. - Source: Hacker News / 9 months ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  Saltcured, find these comments super insightful! > Yeah, there's a lot of hidden magic/assumptions in having a "writable snapshot of a specific version" of production data. That's absolutely a huge assumption. This technology has been a game changer for us: https://lakefs.io/ > It becomes a headache when there is too much contention to use these sandboxes, or too much manual effort to reset them to a desired... - Source: Hacker News / 9 months ago

• Using git to version control experimental data (not code)?

  You should not store your data in git itself, but rather use git to version your data sets. The currently best option for that is (IMHO) https://lakefs.io though there are a few others in various states of usability/maturity. Source: about 1 year ago

• How are you incrementally testing your data pipelines as you develop them?

  I mean if you're ready to adopt a new framework into your ecosystem this is one of the major usecases for LakeFS. Source: over 1 year ago