Live data from Hacker News

MinIO is now in maintenance-mode

github.com

191–200 of 338 posts

Re: MinIO is now in maintenance-mode

#191
post #79

Shocker... they abandoned POSIX compatibility, built a massively over-complicated product, then failed to compete with things like Ceph on the metal side or ubiquitous S3/R2/B2 on the cloud side.

> they abandoned POSIX compatibility, built a massively over-complicated product This is a wild sentence--how can you criticize them for abandoning POSIX support __and__ building a massively over-complicated product? Making a reliable POSIX system is inherently very complex.

What would go in to POSIX compatibility for a product like this which would make it complicated? Because the kind of stuff that stands out to me is the use of Linux specific syscalls like epoll/io_uring vs trad POSIX stuff like poll. That doesn't seem too complicated?

Re: MinIO is now in maintenance-mode

#192
post #87
post #33

They have been removing features from the open source version for a while. The closest alternative seems to be RustFS. Has anyone tried it? I was waiting until they support site replication before switching.

Garage is a popular alternative to Minio. https://garagehq.deuxfleurs.fr I hadn't heard of RustFS and it looks interesting, although I nearly clicked away based on the sheer volume of marketing wank on their main page. The GitHub repo is here: https://github.com/rustfs/rustfs

I saw an article here not long about where someone explained they were hosting their Kopia or Nextcloud aver Garage, but I can't find it anymore.

This was going to be my next project, as I am currently storing my Kopia/Ente on MinIO in a non-distributed way. MinIO project going to shi*s is a good reason to take on this project faster than later.

Re: MinIO is now in maintenance-mode

#193

Earlier quoted context omitted.

> ... it can be forked without any potential license change in the future ... It is useful to remember that one may fork at the commit before a license change.

It is also useful to remember that MinIO has historically held to an absurd interpretation of the AGPL -- that it spreads (again, according to them) to software that communicates with MinIO via the REST API/CLI. I assume forks, and software that uses them will be held to the same requirements.

As long as I'm not the one who gets sued over this, I think it would be wonderful to have some case law on what constitutes an AGPL derivative work. It could be a great thing for free software, since people seem to be too scared to touch the AGPL at all right now.

Re: MinIO is now in maintenance-mode

#194

Earlier quoted context omitted.

> I saw nothing above what Apache Spark+Hadoop with _consistent_ object stores already offers on Amazon (S3), Google Cloud (GCS), and or Microsoft (Azure Storage, ADLS Gen2) it was very simple to setup, and even if you just leased a bunch of servers off say OVH, far FAR cheaper to run your own than paying any of the big cloud providers. It also had pretty low requirements, ceph can do all that but setup is more compl…

MinIO still makes no sense, as Ceph is fundamentally already RADOS at its core (fully compatible with S3 API.) For a proper Ceph setup, even the 45drives budget configuration is still not "hobby" grade. I will have to dive into the MinIO manual at some point, as the value proposition still seems like a mystery. Cheers =3

MinIO is far less complex than getting same functionality on Ceph stack.

But that's kind of advantage only on the small companies and hobbyist market, big company either have enough needs to run big ceph cluster, or to buy it as a service.

Minio is literally "point it at storage(s), done". And at far smaller RAM usage.

Ceph is mon servers, osd servers, then rados gatway server on top of that.

Re: MinIO is now in maintenance-mode

#195
post #160

I've been using Minio in ZeroFS' [0] CI (a POSIX compliant filesystem that works on top of s3). I guess I'll switch to MicroCeph [1]. [0] https://github.com/Barre/ZeroFS [1] https://canonical-microceph.readthedocs-hosted.com/stable/

What is the use case for implementing a POSIX filesystem on top of an object store? I remember reading this article a few years ago, which happens to be by the minio folks: https://blog.min.io/filesystem-on-object-store-is-a-bad-idea...

Re: MinIO is now in maintenance-mode

#196
post #144
post #33

They have been removing features from the open source version for a while. The closest alternative seems to be RustFS. Has anyone tried it? I was waiting until they support site replication before switching.

Although promising, RustFS is a Chinese product. This would be a non-starter for many.

Because they aren't thinking about all the chinese wetware they'd be writing down that decision with.

Re: MinIO is now in maintenance-mode

#197
post #87
post #33

They have been removing features from the open source version for a while. The closest alternative seems to be RustFS. Has anyone tried it? I was waiting until they support site replication before switching.

Garage is a popular alternative to Minio. https://garagehq.deuxfleurs.fr I hadn't heard of RustFS and it looks interesting, although I nearly clicked away based on the sheer volume of marketing wank on their main page. The GitHub repo is here: https://github.com/rustfs/rustfs

We’ve done some fairly extensive testing internally recently and found that Garage is somewhat easier to deploy, but is not as performant at high speeds. IIRC we could push about 5 gigabits of (not small) GET requests out of it, but something blocked it from reaching the 20-25 gigabits (on a 25g NIC) that MinIO could reach (also 50k STAT requests/s)

I don’t begrudge it that. I get the impression that Garage isn’t necessarily focussed on this kind of use case.

Re: MinIO is now in maintenance-mode

#198
post #103

Earlier quoted context omitted.

? Its like GET /object, PUT /object. To me its the most obvious mapping of HTTP to immutable object key value storage you could imagine. It is bad that the control plane responses can be malformed XML (e.g keys are not escaped right if you put XML control characters in object paths) but that can be forgiven as an oversight. Its not perfect but I don't think its a strange API at all.

Last I checked the user guide to the API was 3500 pages. 3500 pages to describe upload and download, basically. That is pretty strange in my book.

Even download and upload get tricky if you consider stuff like serving buckets like static sites, or stuff like siged upload URLs.

Now with the trivial part off the table, let's consder storage classes, security and ACLs, lifecycle management, events, etc.

Re: MinIO is now in maintenance-mode

#199
post #178

Earlier quoted context omitted.

Yeah, that page is horrendous and looks super sketchy. It looks like a very professional fishing attempt to get unsuspecting developers to download malware. They have a lot of obviously fake quotes from non-existent people at positions that don’t even mention what company it is. The pictures are misgendered and even contain pictures of kids. Feels like the whole page is AI generated.

They have a CLA that assigns copyright to them: https://github.com/rustfs/rustfs/blob/5b0a3a07645364d998e3f5... So, arguably worse than MinIO.

The _only_ reason to require a CLA is because you expect to change the license in the future. RustFS has rug-pull written all over it.

Re: MinIO is now in maintenance-mode

#200
post #178

Earlier quoted context omitted.

They have a CLA that assigns copyright to them: https://github.com/rustfs/rustfs/blob/5b0a3a07645364d998e3f5... So, arguably worse than MinIO.

How would you run a project like this? People come and go. People do a one-time contribution and then you never hear from them again. People work on a project for years and then just go silent. Honestly, credit where credit is due, but how is a project like this supposed to manage this?

You could pick a license and not plan to relicense later. Like Linux.
Post reply on HN