Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MinIO is now in maintenance-mode

github.com

Post reply on HN
Print view View original

151–160 of 338 posts

Re: MinIO is now in maintenance-mode

#151

Post by speedgoose »

phoronixrly wrote: post #131
liviux wrote: post #126

Fork in Linux foundation incoming. Minio will revert in 1-2 years, but too late, community will move on and never return, reputation lost forever

Just watch them harass fork users with proprietary stacks as they used to: https://github.com/minio/minio/issues/13308#issuecomment-929... https://github.com/minio/minio/discussions/13571#discussionc...

Oh no, I used MinIO once or twice for some unlicensed software.

Should I contact a MinIO salesman to purchase an enterprise license ASAP or is it fine if I license my kids and advent of code solutions under the AGPLv3 license ?

Re: MinIO is now in maintenance-mode

#152

Post by jerf »

tlarkworthy wrote: post #45
candiddevmike wrote: post #38

It sucks that S3 somehow became the defacto object storage interface, the API is terrible IMO. Too many headers, too many unknowns with support. WebDAV isn't any better, but I feel like we missed an opportunity here for a standardized interface.

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

That may be what S3 is like, but what the S3 API is is this: https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/service/s3

My browser prints that out to 413 pages with a naive print preview. You can squeeze it to 350 pretty reasonably with a bit of scaling before it starts getting to awfully small type on the page.

Yes, there's a simple API with simple capabilities struggling to get out there, but pointing that out is merely the first step on the thousand-mile journey of determining what, exactly, that is. "Everybody uses 10% of Microsoft Word, the problem is, they all use a different 10%", basically. If you sat down with even 5 relevant stakeholders and tried to define that "simple API" you'd be shocked what you discover and how badly Hyrum's Law will bite you even at that scale.

Re: MinIO is now in maintenance-mode

#153

Post by nazcan »

I'm quite interested in a k8s-native file-system that makes use of local persistent volumes. I'm running cockroachDB in my cluster (not yet with local persistent volumes.. but getting closer).

Anyone have any suggestions?

Re: MinIO is now in maintenance-mode

#154

Post by speedgoose »

apexalpha wrote: post #143

So how are HN reviews of GarageHQ? Or any others?

I havn't tested it since a while, but it was pretty good and a lot simpler than MinIO.

Like in the old MinIO days, an S3 object is a file on the filesystem, not some replicated blocks. You could always rebuild the full object store content with a few rsync. I appreciate the simplicity.

My main concern was that you couldn't configure it easily through files, you had to use CLI, which wasn't very convenient. I hope this has changed.

Re: MinIO is now in maintenance-mode

#155

Post by realreality »

apexalpha wrote: post #143

So how are HN reviews of GarageHQ? Or any others?

Garage works well for its limited feature set, but it doesn't have very active development. Apparently they're working on a management UI.

Seaweedfs is more mature and has many interfaces (S3, webdav, SFTP, REST, fuse mount). It's most appropriate for storing lots of small files.

I prefer the command line interface and data/synchronization model of Garage, though. It's easier to manage, probably because the developers aren't biting off more than they can chew.

Re: MinIO is now in maintenance-mode

#156

Post by daveguy »

st3fan wrote: post #60

What a story. EOL the open source foundation of your commercial product, to which many people contributed, to turn it into a closed source "A-Ff*ing-I Store" .. seriously what the ...

This is why I don't bother with AGPL released by a company (use or contribute).

Choosing AGPL with contributors giving up rights is a huge red flag for "hey, we are going to rug pull".

Just AGPL by companies without even allowing contributor rights is saying, "hey, we are going to attempt to squeeze profit out and don't want competition on our SaaS offering."

I wish companies would stop trying to get free code out of the open source community. There have been so many rug pulls it should be expected now.

Re: MinIO is now in maintenance-mode

#157

Post by realreality »

speedgoose wrote: post #154
apexalpha wrote: post #143

So how are HN reviews of GarageHQ? Or any others?

I havn't tested it since a while, but it was pretty good and a lot simpler than MinIO. Like in the old MinIO days, an S3 object is a file on the filesystem, not some replicated blocks. You could always rebuild the full object store content with a few rsync. I appreciate the simplicity. My main concern was that you couldn't configure it easily through files, you had to use CLI, which wasn't very convenient. I hope thi…

Objects in Garage are broken up into 1MB (default) blocks, and compressed with zstandard. So, it would be difficult to reconstruct the files. I don't know if that was a recent change since you looked at it.

Configuration is still through the CLI, though it's fairly simple. If your usecase is similar to the way that the Deuxfleurs organization uses it -- several heterogeneous, geographically distributed nodes that are more or less set-it-and-forget-it -- then it's probably a good fit.

Re: MinIO is now in maintenance-mode

#158

Post by paulddraper »

binsquare wrote: post #97
st3fan wrote: post #60

What a story. EOL the open source foundation of your commercial product, to which many people contributed, to turn it into a closed source "A-Ff*ing-I Store" .. seriously what the ...

I still don't understand what the difference is. What is an AI Stor (e missing on purpose because that is how it is branded: https://www.min.io/product/aistor )

It can store things for AI workloads (and non-AI workloads, but who’s counting…)

Re: MinIO is now in maintenance-mode

#159

Post by [deleted] »

throwaway894345 wrote: post #108
aftbit wrote: 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.

[deleted]
Post reply on HN