←back to thread

672 points LexSiga | 1 comments | | HN request time: 0.208s | source
Show context
ezascanbe ◴[] No.45666985[source]
Full disclosure: I work for Cloudian.

While I understand the frustration with MinIO’s approach here, I want to be upfront about what Cloudian HyperStore is and isn’t - it is designed for multi-node, multi-site deployments (think 3+ nodes minimum) and performs best on bare metal or dedicated infrastructure rather than containerized environments.

It’s a very mature S3 and offers IAM, SQS and STS endpoints as well.

If you’re running MinIO at scale in production and looking at migration options, I’m happy to connect you with our team who can discuss whether HyperStore makes sense for your use case. That said, for single-node dev environments or lightweight deployments that many here are using MinIO for, the community alternatives mentioned in this thread are probably better fits. Different tools for different scales. Happy to answer any technical questions about HyperStore’s architecture if helpful.

replies(2): >>45667008 #>>45670224 #
killingtime74 ◴[] No.45667008[source]
What is Cloudian? You guys didn't develop Minio did you? (Google says Minio Inc?) If you did it's hard to tell.
replies(1): >>45667050 #
ezascanbe ◴[] No.45667050[source]
No, Cloudian did not develop MinIO - completely separate companies. MinIO was developed by MinIO Inc. Cloudian makes HyperStore, which is our own S3-compatible object storage solution. We’re a competitor to MinIO, not affiliated with them in any way.
replies(1): >>45667074 #
1. killingtime74 ◴[] No.45667074[source]
Ah I see. Will check yours out.