Just finished installing it on my OpenIndiana NAS to replace Minio.<p>Biggest difference so far is that Minio is just files on disk, Garage chunks all files and has a metadata db.<p>Minios listing operations were horribly slow, still have to see if Garage resolves that.
A very good alternative is seaweedfs <a href="https://github.com/chrislusf/seaweedfs/" rel="nofollow">https://github.com/chrislusf/seaweedfs/</a> based on facebook haystack paper (efficient small files) & more.
It looks similar to minio, which as also an AGPL single binary that implements the S3 API. However Minio is written in Go and Garage is in Rust. I'd love to see a detailed comparison.
Do we know the largest size of data that these object stores have handled? People seem have been moving away from HDFS, yet companies could host exabytes of data on HDFS and serve TBs of scans per second with a single team of fewer than 15 people. I was wondering how production-ready the other OSS alternatives are for such scale of data.
I remember working at a company that got started before cloud took off. They used mogile fs which I recently found at <a href="https://mogilefs.github.io/mogilefs-docs/HighLevelOverview.html" rel="nofollow">https://mogilefs.github.io/mogilefs-docs/HighLevelOverview.h...</a> but I never hear about anyone else using it. It wasn't as stable as S3 but it was okay, I guess. Does anyone else here remember that distributed open source file system?
So is this supposed to be a simpler, less "omg you need a full time staff of 10 to manage" version of Ceph?<p><a href="https://docs.ceph.com/en/quincy/" rel="nofollow">https://docs.ceph.com/en/quincy/</a>
For this use-case, I like JuiceFS better.<p>* <a href="https://juicefs.com/en/" rel="nofollow">https://juicefs.com/en/</a><p>* <a href="https://github.com/juicedata/juicefs" rel="nofollow">https://github.com/juicedata/juicefs</a><p>I am not affiliated with them, just a regular user.