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!
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
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.