Top
Best
New

Posted by hajtom 12/3/2025

MinIO is now in maintenance-mode(github.com)
511 points | 322 commentspage 3
killme2008 12/3/2025|
I can't believe they made this decision. It's detrimental to the open-source ecosystem and MinIO users, and it's not good for them either, just look at the Elasticsearch case.
frellus 12/3/2025||
https://aistore.nvidia.com
positisop 12/3/2025|
github.com/NVIDIA/aistore

At the 1 billion valuation from the previous round, achieving a successful exit requires a company with deep pockets. Right now, Nvidia is probably a suitable buyer for MinIO, which might explain all the recent movements from them. Dell, Broadcom, NetApp, etc, are not going to buy them.

thway15269037 12/3/2025||
So, when anyone will fork in? Call it MaxIO or whatever. I might even submit couple of small patches.

My only blocker for a fork to maintain compatibility and path to upgrade from earlier versions.

12_throw_away 12/3/2025|
To be fair, their previous behavior and attitude towards the open source license suggests that minio would possibly engage in at least a little bumptious legal posturing against whoever chose to fork it.
valyala 12/3/2025||
What is the purpose of MinIO, Seaweedfs and similar object storage systems? They lack durability guarantees provided by S3 and GCS. They lack "infinite" storage promise contrary to S3 and GCS. They lack "infinite" bandwidth unlike S3 and GCS. They are more expensive than other storage options, unlike S3 and GCS.
cortesoft 12/3/2025||
We use it because we are already running our own k8s clusters in our datacenters, and we have large storage requirements for tools that have native S3 integration, and running our own minio clusters in the same datacenter as the tools that generate and consume that data is a lot faster and cheaper than using S3.

For example, we were running a 20 node k8s cluster for our Cortex (distributed Prometheus) install, monitoring about 30k servers around the world, and it was generating a bit over a TB of data a day. It was a lot more cost effective and performant to create a minio cluster for that data than to use S3.

Also, you can get durability with minio with multi cluster replication.

valyala 12/4/2025||
Consider migrating to VictoriaMetrics and saving on storage costs and operations costs. You also won't need MinIO, since it stores data to local filesystem (aka to regular persistent volumes). See real-world reports from happy users who saved costs on a large-scale Prometheus-compatible monitoring - https://docs.victoriametrics.com/victoriametrics/casestudies...
cortesoft 12/5/2025||
I can't imagine switching at this point. We spent quite a while building up our Cortex and Minio infrastructure management, as well as our alerting and inventory management systems, and it is all very stable right now. We don't really touch it anymore, it just hums along.

We have already worked through all the pain points and it all works smoothly. No reason to change something that isn't a problem.

onionisafruit 12/3/2025|||
I haven't used it in a while, but it used to be great as a test double for s3
wasmitnetzen 12/3/2025|||
S3 is a widely supported API schema, so if you need something on-prem, you use these.
valyala 12/4/2025||
But what's the point to use these DIY object storage systems, when they do not provide durability and other important guarantees provided by S3 and GCS?
lima 12/4/2025||
When you want just the API for compatibility, I guess?

Self-hosted S3 clones with actual durability guarantees exist, but the only properly engineered open source choices are Ceph + radosgw (single-region, though) or Garage (global replication based on last-writer-wins CRDS conflict resolution).

maartin0 12/3/2025|||
It's great for a prototype which doesn't need to store a huge amount of data, you can run it on the same VM as a node server behind Cloudflare and get a fairly reliable setup going
spapas82 12/3/2025||
Minio allows you to have an s3 like interface when you have your own servers and storage.
valyala 12/4/2025||
MinIO also allows losing your data, since it doesn't provide high durability guarantees unlike S3 and GCS.
lynn_xx 12/4/2025||
MinIO is a great open-source project. I’m familiar with it because I previously worked with Longhorn. But for any project to sustain long-term development, it needs a viable business model to support ongoing investment and growth.
ecshafer 12/3/2025||
Is this just the open source portion? Minio is now a fully paid product then?
0x073 12/3/2025||
"For enterprise support and actively maintained versions, please see MinIO AIStor."

Probably yes.

margorczynski 12/3/2025||
Basically officially killing off the open source version.
pabs3 12/4/2025||
Anyone know if MinIO AIStor is legal? AFAICT MinIO didn't have a CLA and there are 559 non-@minio.io commit authors in the git history, which could be an AGPL violation if they didn't get contributor approval for the license change. Or is AIStor a fresh codebase written from scratch?

Edit: some discussion of this here: https://news.ycombinator.com/item?id=46136871

EgoIncarnate 12/4/2025|
MinIO had a de facto CLA. MinIO required contributors to license their code to the project maintainers (only) under Apache 2. Not as bad as copyright assignment, but still asymmetric (they can relicense for commercial use, but you only get AGPL). https://github.com/minio/minio/blob/master/.github/PULL_REQU...
Eikon 12/3/2025||
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/

ahepp 12/3/2025|
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...
Eikon 12/3/2025||
> What is the use case for implementing a POSIX filesystem on top of an object store?

The use case is fully stateless infrastructure: your file/database servers become disposable and interchangeable (no "pets"), because all state lives in S3. This dramatically simplifies operations, scaling, and disaster recovery, and it's cheap since S3 (or at least, S3 compatible services) storage costs are very low.

The MinIO article's criticisms don't really apply here because ZeroFS doesn't store files 1:1 to S3. It uses an LSM-tree database backed by S3, which allows it to implement proper POSIX semantics with actual performance.

ahepp 12/3/2025||
It makes sense that some of the criticisms wouldn't apply if you're not storing the files 1:1.

What about NFS or traditional filesystems on iSCSI block devices? I assume you're not using those because managing/scaling/HA for them is too painful? What about the openstack equivalents of EFS/EBS? Or Ceph's fs/blockdev solutions (although looking into it a bit, it seems like those are based on its object store)?

rowanseymour 12/3/2025|
What's the simplest replacement for mocking S3 in CI? We don't about performance or reliability.. it's just gotta act like S3.
onei 12/3/2025||
I've used localstack in the past which worked pretty well.

https://github.com/localstack/localstack

rodwyersoftware 12/3/2025||
localstack, 100%
More comments...