Note di Matteo

Altri feedback sulle alternative a MinIO, ora definitivamente abbandonato nella versione open source, da Hacker News.

Un confronto tra le principali alternative (vedi anche miei post precedenti):

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 the fastest in the object storage field.

2. The installation for Garage and SeaweedFS is more complex compared to RustFS.

3. The RustFS console is the most convenient and user-friendly.

4. Ceph is too difficult to use; I wouldn't dare deploy it without a deep understanding of the source code.

Although many people criticize RustFS, suggesting its CLA might be "bait," I don't think such a requirement is excessive for open source software, as it helps mitigate their own legal risks.

Furthermore, Milvus gave RustFS a very high official evaluation. Based on technical benchmarks and other aspects, I believe RustFS will ultimately win.

https://milvus.io/blog/evaluating-rustfs-as-a-viable-s3-compatible-object-storage-backend-for-milvus.md

Un po' di promozione dall'autore di SeaweedFS:

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

How to build a distributed queue in a single JSON file on object storage. Usare l'object storage come un database è sempre affascinante e Turbopuffer ci ha costruito sopra un vector db. Ora hanno implementato anche la coda di indicizzazione dei dati in un singolo file queue.json in un bucket S3/GCS, sfruttando le primitive dell'object storage (come compare-and-set, o CAS) per gestire conflitti (è in realtà un po' più complicato di così e l'articolo è scritto molto bene).

Alternatives to MinIO for single-node local S3 analizza e confronta le principali alternative a MinIO dopo la chiusura della versione open source. In estrema sintesi:

New Rusty object stores confronta anche a livello tecnico rustfs e Garage. Contesto molto utile per capire la natura dei progetti.

SeaweedFS Intro Slides è un'introduzione a SeaweedFS e la sua architettura.

Dopo Quickwit scopro Nixiesearch, essenzialmente un Elasticsearch backed by object storage (S3, ecc.).

SlateDB. slatedb is an OSS embedded key-value database built on object storage.

E alla fine MinIO versione community è improvvisamente abbandonato. Ci è voluto poco.

Numeri sulla migrazione di Mezmo da Elasticsearch a Quickwit.

Con Elasticsearch:

• 2 PB di storage
• 275 istanze EC2
• 35 TB di RAM
• 7770 core

(800 MB - 2 GB di integestion al secondo)

Con Quickwit (che è pazzesco!):

• -80% storage
• -40% di instanze EC2
• -98% RAM
• -93% CPU

Storia molto interessante di scaling: come Nanit ha risparmiato 500mila $ all'anno implementando un S3 in memoria, e i problemi di scaling (networking e memory leak) incontrati una volta deployato con il traffico in produzione di diversi GB/s.

Alternative a MinIO:

• rustfs
• Garage
• SeaweedFS

MinIO sta diventando crescentemente un progetto prevalentemente commerciale:

• MinIO removed web management features from its open-source community version, forcing users to command-line tools or paid upgrades
• MinIO Community version was downgraded to basic object browser only with no account management, policy configuration, or administrative functions
• The cost of MinIO’s paid version is substantial: software and support alone cost a MINIMUM of $96,000 per year, rising to $244,032 per year for 1 PB of usable capacity, according to MinIO’s website.

Ora la versione community non è più su Docker Hub ed è sparita anche la documentazione community apparentemente.