Ask HN: Is there any good open-source alternative to MinIO?
5 comments
I'm thinking maybe SeaweedFS [0, 2] or Versity Gatweway [1, 3] or RustFS [4].
Seems there are other options, too, e.g. Garage [5].
I only used MinIO briefly in the past, but it was good/worked, and I do plan to set up S3 blob storage again soon.
[0] https://github.com/seaweedfs/seaweedfs
[1] https://github.com/versity/versitygw
[2] https://blog.elest.io/rustfs-vs-seaweedfs-vs-garage-which-mi...
[3] https://news.ycombinator.com/item?id=47806348
[4] https://github.com/RustFS/RustFS
[5] https://git.deuxfleurs.fr/Deuxfleurs/garage
Seems there are other options, too, e.g. Garage [5].
I only used MinIO briefly in the past, but it was good/worked, and I do plan to set up S3 blob storage again soon.
[0] https://github.com/seaweedfs/seaweedfs
[1] https://github.com/versity/versitygw
[2] https://blog.elest.io/rustfs-vs-seaweedfs-vs-garage-which-mi...
[3] https://news.ycombinator.com/item?id=47806348
[4] https://github.com/RustFS/RustFS
[5] https://git.deuxfleurs.fr/Deuxfleurs/garage
Thanks a bunch! Currently I'm weighing SeaweedFS vs RustFS, and if I just wanted S3-compatible API, I'd probably go with RustFS although it's not so mature yet, but with WebDAV and some other stuff, and favoring stability and reliability, looks like I'm leaning more towards SeaweedFS.
I build https://github.com/uroni/hs5 as replacement for single node use with a focus on high performance. I list other alternatives in the README there. Some short version:
Ceph: Robust, widely used for multi-node deployments. Would recommend for serious use.
RustFS: As an in-place replacement using the same storage format. Though, to me it is a bit suspect, e.g. if it uses fsync for durability.
seaweedfs: Multi-node alternative, that keeps the object mapping in memory (so more RAM usage and startup cost compared to alternatives).
Garage: Multi-node alternative, web-interface available separately. To me seems unsuitable for single-node use at this point.
VersityGW: Single-node alternative, which uses the same object=file in file system tree storage as MinIO (with the same disadvantages/advantages). It uses extended attributes for S3 metadata, so less filesystem overhead than MinIO/RustFS at least. Cannot find any Sync() or fsync calls in the code, though.
Ceph: Robust, widely used for multi-node deployments. Would recommend for serious use.
RustFS: As an in-place replacement using the same storage format. Though, to me it is a bit suspect, e.g. if it uses fsync for durability.
seaweedfs: Multi-node alternative, that keeps the object mapping in memory (so more RAM usage and startup cost compared to alternatives).
Garage: Multi-node alternative, web-interface available separately. To me seems unsuitable for single-node use at this point.
VersityGW: Single-node alternative, which uses the same object=file in file system tree storage as MinIO (with the same disadvantages/advantages). It uses extended attributes for S3 metadata, so less filesystem overhead than MinIO/RustFS at least. Cannot find any Sync() or fsync calls in the code, though.
At least on ZFS, VersityGW absolutely does use sync IO, found it out the hard way on an HDD zpool with no SLOG...
did u hear about pramaat
But given the current situation (https://news.ycombinator.com/item?id=46136023), and given there probably has been new entrants into the ecosystem since then, what are people using today as MinIO alternatives?
I'm using an old version of MinIO today, mainly because of the S3-api + simple webui, so something that does the same, but more friendly to FOSS, would be great!