AWS S3 open source alternative written in Go

Post by mrweasel » Wed, Aug 31, 2016, 7:50 AM UTC

matthewrudy wrote: post #105

brianwawok wrote: post #73

Earlier quoted context omitted.

There really are pros to on prem. There are cons, don't get me wrong, but to somehow claim that AWS is the end all be all of hosting choices is demonstrably wrong. For example - You want to develop a financial exchange with a 100 microsecond average response time, peaks of 10Gbit traffic, and 5 9s of uptime. Do you host that on AWS? I wouldn't. Another example - If I were a medium+ sized company (say 20+ employees),…

Re: github I can understand why on-premises git is better in some ways. But you're overstating the frequency of github outages. And it doesn't exactly kill the business when it's down for an hour. Git is distributed after all.

Post by vacri » Wed, Aug 31, 2016, 8:05 AM UTC

matt_wulfeck wrote: post #86

vacri wrote: post #72

Earlier quoted context omitted.

On-Premises is also "one less third-party service to manage". I work for a small company, and was asked to list the external services we use a couple of days ago, and the list went into dozens. It's not the primary reason for On Premises, but it's one less thing to worry about: "our tech team has full control, instead of yet another company having some control that we can't see"

I would argue that from a management point of view it's actually a lot nicer for small places to offload to third parties. As a point, my original comment pointed out that somebody else is on-call for that services uptime.

Post by espadrine » Wed, Aug 31, 2016, 9:28 AM UTC

fizzbatter wrote: post #84

brightball wrote: post #30

Earlier quoted context omitted.

I've been wondering about this for that use case myself: https://ipfs.io/

Yea IPFS is awesome, i have often pondered about the idea of using it for an internal family storage.

Post by espadrine » Wed, Aug 31, 2016, 9:35 AM UTC

diggan wrote: post #126

espadrine wrote: post #125

Earlier quoted context omitted.

Does it support encryption yet? Also, you'd have to auto-pin all your files, or risk losing them. I think GlusterFS (battle-proof, but file-wise and assumes an administrator with access to everything) assumes or infinit.sh (robust ACL, but young, not open-source) better addresses those use-cases.

Encrypt the files before adding to IPFS and then decrypt after receiving them. Support for encryption will be built-in into IPFS in the future but for now, this solution works. There is a issue tracking this here: https://github.com/ipfs/faq/issues/6 Also, when adding files yourself, those files become pinned by the default. Getting files won't pin automatically however. You have some more information about pinning h…

Post by cookiengineer » Wed, Aug 31, 2016, 10:20 AM UTC

y4m4b4 wrote: post #87

cyphar wrote: post #83

Earlier quoted context omitted.

Then why not make the license AGPLv3-or-later, to avoid other people creating proprietary forks? I get that it's not a common occurence within the Golang world, but nothing will change unless more Golang projects start making their code copylefted.

GNU AGPL is an ideal license for free software projects. We are a strong supporter of the GNU project. We chose Apache License for Minio purely for adoption reasons. Most of our users build proprietary software around Minio and their legal council has a default NO policy towards GNU licenses. Besides, FSF has also approved Apache License v2 as a free software license. Proprietary forks are OK with us. It will be too…