5 ms·
One will wish to be cautious, as they recently changed their license to AGPL-3.0: https://github.com/minio/minio/blob/master/LICENSE https://github.com/minio/mi
by mdaniel 5y ago
One will wish to be cautious, as they recently changed their license to AGPL-3.0: https://github.com/minio/minio/blob/master/LICENSE https://github.com/minio/minio/blob/master/LICENSE because they're afraid of AWS offering Minio as a hosted service, I guess
- tyingq 5y agoThat seems okay, since you can use any S3 client library. So, good advice, but probably very few folks would have a need to touch the server side source. Minio's client side libraries appear to be packaged separately, and Apache licensed: https://github.com/minio/minio-go https://github.com/minio/minio-go https://github.com/minio/minio-js https://github.com/minio/minio-js (Etc)
- whateveracct 5y agoAnd if you do touch the server-side code..do it in an open source fork?
- syshum 5y agoWhy would AWS offer Minio, a clone of an AWS Service, as a service? That seems very confusing
- MonkeyClub 5y agoSo that AWS can still get people to pay subscription fees to them, instead of using their own hardware with a FOSS solution, if MinIO becomes too popular.
- remram 5y agoI don't understand. Aren't you describing S3? Why would Amazon offer a second version of S3?
- cyberge99 5y agoSelf hosted as a feature. Akin to managed vs colo hosting.
- motives 5y agoThey pretty much already offer this with outposts (its technically their hardware but its on your premises).
- remram 5y agoBy "self-hosted" you still mean still running on AWS hardware? I don't understand. Why would anybody pay EBS rates instead of S3 rates, to get data stored in the same place by the same people?
- deleted 5y ago[deleted]
- hdjjhhvvhga 5y agoI understood it as a joke referencing Aamazon's tendency to take just any open source product that happens to gain enough popularity, rename it and offer it as a shiny new feature of AWS.
- remram 5y agoAmazon wouldn't, but another cloud service might decide to run this rather than implementing their own S3-compatible object storage from scratch. Or they might use part of Minio's code to make their existing object storage solution compatible with S3.
- adolph 5y agoIIRC from this podcast with Anand Babu Periasamy [0], they already do. https://www.dataengineeringpodcast.com/minio-object-storage-episode-99/ https://www.dataengineeringpodcast.com/minio-object-storage-...
- marcinzm 5y agoThey more likely afraid of smaller and upcoming cloud providers offering it as an S3 drop in.
- corobo 5y agoThis plus CDNs I'd imagine too. S3 protocol is the new FTP and minio ticks the box quickly, they want their share of that (and deserve it imo)
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- benlivengood 5y agoUnless you're running a locally patched version AGPL is indistinguishable from GPL.
- kkielhofner 5y agoWhile this is true a word of warning: if you ever end up in a due diligence situation or a source code audit AGPL can really freak people out and hang up/derail the process until you get them to understand this point. If you can at all.
- OJFord 5y agoI'm pretty sure that - the prospect of AWS hosting and rebranding minio - was a joke.
- deleted 5y ago[deleted]
- gunapologist99 5y agoPretty sure AWS would like to have something that at least looks and feels sorta like S3. And, being S3-compatible at an API level would be a big bonus for a company the size of AWS, especially if it had nearly native compatibility with the aws-cli tool.