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

MinIO repository is no longer maintained

github.com

Post reply on HN
Print view View original

341–350 of 397 posts

Re: MinIO repository is no longer maintained

#341

Post by chrislusf »

I work on SeaweedFS since 2011, and full time since 2025.

SeaweedFS was started as a learning project and evolves along the way, getting ideas from papers for Facebook Haystack, Google Colossus, Facebook Tectonics. With its distributed append-only storage, it naturally fits object store. Sorry to see MinIO went away. SeaweedFS learned a lot from it. Some S3 interface code was copied from MinIO when it was still Apache 2.0 License. AWS S3 APIs are fairly complicated. I am trying to replicate as much as possible.

Some recent developments:

* Run "weed mini -dir=xxx", it will just work. Nothing else to setup.

* Added Table Bucket and Iceberg Catalog.

* Added admin UI

Re: MinIO repository is no longer maintained

#342

Post by chrislusf »

ElDji wrote: post #150

I successfully migrated from MinIO to Ceph, which I highly recommend. Along the way, I tested SeaweedFS, which looked promising. However, I ran into a strange bug, and after diagnosing it with the help of Claude, I realized the codebase was vibe-coded and riddled with a staggering number of structural errors. In my opinion, SeaweedFS should absolutely not be used for anything beyond testing — otherwise you're almost…

(I work on SeaweedFS.)

Haha, you used Claude to find the Clause code.

I used Claude to generate a lot of admin UI pages, saved a lot of time. The core storage engine part I dare not using AI, same as you.

Re: MinIO repository is no longer maintained

#343

Post by chrislusf »

rietta wrote: post #240

What is the best alternative that can run as a Docker image that mimics AWS S3 to enable local only testing without any external cloud connections? For me, my only use for Minio was to simulate AWS S3 in docker compose so that my applications were fully testable locally. I never used it it production or as a middle ware. It has not sat well with me to use alternative strategies like Ruby on Rails' local file storage…

I work on SeaweedFS.

I am trying to support AWS S3 APIs as complete as possible.

Recently added support for Table Bucket, besides myriads of details, such as policies, STS, IAM, OIDC, WORM, lock and versioning, governance, etc.

Re: MinIO repository is no longer maintained

#345

Post by yjftsjthsd-h »

victormy wrote: post #334
everfrustrated wrote: post #313

Earlier quoted context omitted.

RustFS has rug-pull written all over it. You can bookmark this comment for the future. 100% guaranteed it will happen. Only question is when.

Lol, maybe you should fund the RustFS team yourself or sponsor a top-tier legal team for them. If you can help them rewrite their CLAs and guarantee they'll never face any IP risks down the road, then sure, you're 100% right.

And again - what IP risk does a CLA solve, that a DCO wouldn't? Like, IANAL so I certainly could be missing something, but I'd like to hear what it might be.

Re: MinIO repository is no longer maintained

#346

Post by tom_m »

I agree with others, it's perfectly fine for a project to stop being open source.

That said, we also can't blame people for using open source without paying or donating.

I can absolutely take issue with people demanding things of open source projects. They can contribute or pay if they want to be demanding around bug fixes and support.

I've been a big proponent of open source for many years - learning from, contributing to, maintaining, sharing my own projects for free as open-source. I don't expect anything in return.

In fact, open-source projects benefit from contributors. So to me it's a bit incompatible with taking money. Money for what? For who? If it supports the project I'm ok with that, but I've also seen it line the pockets of original authors. I've seen original authors then turn other people's contributions through hard work into a business.

There is a very line between a funded community project and getting free labor for a business.

I take serious issue with open source projects magically one day turning into a business build on the backs of others for free. Not saying that about minIO or any other project. I'm just saying that happens.

Re: MinIO repository is no longer maintained

#347

Post by meotimdihia »

victormy wrote: post #236

First off, I don't think there is anything wrong with MinIO closing down its open source. There are simply too many people globally who use open source without being willing to pay for it. I started testing various alternatives a few months ago, and I still believe RustFS will emerge as the winner after MinIO's exit. I evaluated Garage, SeaweedFS, Ceph, and RustFS. Here are my conclusions: 1. RustFS and SeaweedFS are…

It looks like this article is biased. It only benchmarked RustFS.

In my experience, SeaweedFS has at least 3–5× better performance than MinIO. I used MinIO to host 100 TB of images to serve millions of users daily.

Re: MinIO repository is no longer maintained

#348

Post by __turbobrew__ »

gunapologist99 wrote: post #267
victormy wrote: post #236

First off, I don't think there is anything wrong with MinIO closing down its open source. There are simply too many people globally who use open source without being willing to pay for it. I started testing various alternatives a few months ago, and I still believe RustFS will emerge as the winner after MinIO's exit. I evaluated Garage, SeaweedFS, Ceph, and RustFS. Here are my conclusions: 1. RustFS and SeaweedFS are…

Garage installation is easy. 1. Download or build the single binary into your system (install like `/usr/local/sbin/garage`) 2. Create a file `/etc/garage.toml`: metadata_dir = "/data/garage/meta" data_dir = "/data/garage/data" db_engine = "sqlite" replication_factor = 1 rpc_bind_addr = "[::]:3901" rpc_public_addr = "127.0.0.1:3901" rpc_secret = "[your rpc secret]" [s3_api] s3_region = "garage" api_bind_addr = "[::]:…

Regarding aistore the recommended prod configuration is kubernetes, which brings in a huge amount of complexity. Also, one person (Alex Aizman) has about half of the total commits in the project, so it seems like the bus factor is 1.

I could see running Aistore in single binary mode for small deployments, but for anything large and production grade I would not touch Aistore. Ceph is going to be the better option IMO, it is a truly collaborative open source project developed by multiple companies with a long track record.

Re: MinIO repository is no longer maintained

#349

Post by __turbobrew__ »

dathinab wrote: post #281
victormy wrote: post #236

First off, I don't think there is anything wrong with MinIO closing down its open source. There are simply too many people globally who use open source without being willing to pay for it. I started testing various alternatives a few months ago, and I still believe RustFS will emerge as the winner after MinIO's exit. I evaluated Garage, SeaweedFS, Ceph, and RustFS. Here are my conclusions: 1. RustFS and SeaweedFS are…

> 4. Ceph [...] MinIO was more for the "mini" use case (or more like "anything not large scale", with a very broad definition of large scale). Here "works out of the box" is paramount. And Ceph is more for the maxi use case. Here in depth fine tuning, highly complex setups, distributed setups and similar are the norm. Hence out of the box small scale setup experience is bearly relevant. So they really don't fill out…

Definitely, ceph shines in the 1-100 petabyte range whereas minio excelled in the 0-1 petabyte range.

Re: MinIO repository is no longer maintained

#350

Post by __turbobrew__ »

kyyol wrote: post #327
victormy wrote: post #236

First off, I don't think there is anything wrong with MinIO closing down its open source. There are simply too many people globally who use open source without being willing to pay for it. I started testing various alternatives a few months ago, and I still believe RustFS will emerge as the winner after MinIO's exit. I evaluated Garage, SeaweedFS, Ceph, and RustFS. Here are my conclusions: 1. RustFS and SeaweedFS are…

I run Ceph in my k8s cluster (using rook) -- 4 nodes, 2x 4TB enterprise SSDs on each node. It's been pretty bulletproof; took some time to set up and familiarize with Ceph but now it's simple to operate. Claude Code is amazing at managing Ceph, restoring, fixing CRUSH maps, etc. It's got all the Ceph motions down to a tee. With the tools at our disposal nowadays, saying "I wouldn't dare deploy it without a deep under…

If you setup ceph correctly (multiple failure domains, correct replication rules across failure domains, monitors spread across failure domain, osds are not force purged) it is actually pretty hard to break it. Rook helps a lot too as rook makes it easier to set up ceph correctly.
Post reply on HN