Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Biggest difference so far is that Minio is just files on disk

Minio _was_ just files on disk. They don't support that mode anymore since 2022-10-29 (see the big yellow warning box at [1]).

[1] https://min.io/docs/minio/linux/operations/install-deploy-ma...



Yeah, I have actually frozen Minio at this older version in my stack, as "just files on disk" was the primary feature that drew me to it. I don't want my data locked into some custom format. I'd be willing to bet that ZFS will still be supported in 20 years, but I would not make the same bet about Minio.

For the same reason, it looks like Garage is not an option for my use case.


I use this "just files on disk" feature too, I also use ZFS.

I have a bunch of crawlers uploading data to AWS S3, but S3 is too expensive, I replaced S3 with MinIO.

MinIO stores plain files on disk, which makes it a lot easier to access my data. I can read files without calling MinIO APIs, the speed is super fast.

By the way, which old version are you using? I'm using RELEASE.2022-04-26T01-20-24Z


Well... right now I am using minio version RELEASE.2021-08-31T05-46-54Z. However I really ought to upgrade that to the last supported version.


Ah interesting. I found it appealing to always have a way to get at the data natively as a worst case for restores. The whole use case is for Vertical Backup (from the maker of Duplicacy) to back up VMs.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: