Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by fweespeech | Hacker News Reader

Full thread

fweespeech·

While the concept is interesting, it hasn't built the only real detail that matters from an Object Store perspective:

Cheap, Multi-Datacenter, Performant, Highly Available storage.

"YAS3I" / Yet-Another-S3-Implementation isn't really compelling even if it is open source.

I can pull that out of https://wiki.openstack.org/wiki/Swift/APIFeatureComparison#A...

if I really need that.

View on HN

We are in an early stage, we will have a distributed version by end of this year.

It isn't about "YAS3I". It isn't compatible just for the compatibility sake.

Minio implementation is opinionated: "There is only one way to do it". Given a choice between Amazon S3 and OpenStack SwiftAPI compatibility, we picked Amazon S3. As SwiftAPI gains adoption, we may switch over to SwiftAPI, but will have to drop S3 then. Let the community decide.

Tiny piece of advice, declaring a possible total revamp of the API as soon as you launch might not be the best way to attract early users.

Advice accepted. The choice is for the community to make, we will not make that choice unless community strongly wants us to do so.

From working at an Openstack startup for a while, I can say that customers definitely prefer the S3 API since it works with their existing tools. That being said, they are largely compatible until you get into the authorization models, and the fact that S3 is globally namespaced, whereas Swift scopes names to tenants.

Reply on news.ycombinator.com