Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS S3 open source alternative written in Go

minio.io

Post reply on HN
Print view View original

71–80 of 139 posts

Re: AWS S3 open source alternative written in Go

#71

Post by notyourwork »

davidu wrote: post #46

Theory here is that people will build apps that talk to S3. But sometimes those apps might need to run inside the perimeter and can't talk to the cloud. So rather than rewrite an app to talk to a new internal datastore, you just point it at a locally hosted Minio and you're up and running. Smart.

What kind of situations do you see this becoming a factor in? 5 or 10 years ago this was an issue with early cloud adopters. Now a days cloud providers are ramping up their DCs to be compliant and allow companies/government entities with strict policies to still onboard.

Its a good strategy but not one that I see being exercised frequently enough.

Re: AWS S3 open source alternative written in Go

#72

Post by vacri »

abakker wrote: post #61
matt_wulfeck wrote: post #59

Earlier quoted context omitted.

If you don't mind me asking, why not use Amazon S3? It's cheap and -- importantly -- somebody else is on-call for its uptime.

I'm going to guess that it is part of the "on premises superstition" where companies feel that the stuff they own is more secure somehow. Obviously, this is not often true in practice, but 5 years of research/consulting has taught me that they feel this way all the same. Occasionally, there are laws that also mandate certain controls that cloud providers in general did not have. That is also becoming rarer as time go…

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"

Re: AWS S3 open source alternative written in Go

#73

Post by brianwawok »

abakker wrote: post #61
matt_wulfeck wrote: post #59

Earlier quoted context omitted.

If you don't mind me asking, why not use Amazon S3? It's cheap and -- importantly -- somebody else is on-call for its uptime.

I'm going to guess that it is part of the "on premises superstition" where companies feel that the stuff they own is more secure somehow. Obviously, this is not often true in practice, but 5 years of research/consulting has taught me that they feel this way all the same. Occasionally, there are laws that also mandate certain controls that cloud providers in general did not have. That is also becoming rarer as time go…

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), I would want my source control 100% on prem (excluding backup). Internet connections are too flakey, and Github gets DDOSed too often. I could not stake my entire business on github.

Re: AWS S3 open source alternative written in Go

#74

Post by merb »

Ixiaus wrote: post #47

Or, run Riak with their S3 compatibility layer. Riak is extremely stable and the work Basho has done to make a truly robust distributed database is significant. http://docs.basho.com/riak/cs/2.1.1/

guess it's possible, but riak is not designed to run on a single node. Guess even basho suggests using at least a 5 node cluster.

Re: AWS S3 open source alternative written in Go

#75

Post by tomjakubowski »

davidu wrote: post #46

Theory here is that people will build apps that talk to S3. But sometimes those apps might need to run inside the perimeter and can't talk to the cloud. So rather than rewrite an app to talk to a new internal datastore, you just point it at a locally hosted Minio and you're up and running. Smart.

Versions of this (S3-compatible service for development use) have existed for years. One I used was https://github.com/jubos/fake-s3

Re: AWS S3 open source alternative written in Go

#76

Post by viraptor »

Ixiaus wrote: post #47

Or, run Riak with their S3 compatibility layer. Riak is extremely stable and the work Basho has done to make a truly robust distributed database is significant. http://docs.basho.com/riak/cs/2.1.1/

Other alternatives:

ceph - http://docs.ceph.com/docs/master/radosgw/s3/

swift - https://wiki.openstack.org/wiki/Swift/APIFeatureComparison#A...

Re: AWS S3 open source alternative written in Go

#77

Post by breakingcups »

brianwawok wrote: post #73
abakker wrote: post #61

Earlier quoted context omitted.

I'm going to guess that it is part of the "on premises superstition" where companies feel that the stuff they own is more secure somehow. Obviously, this is not often true in practice, but 5 years of research/consulting has taught me that they feel this way all the same. Occasionally, there are laws that also mandate certain controls that cloud providers in general did not have. That is also becoming rarer as time go…

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),…

I'll give you another pro, customization. Our on-prem Jira instance can have add-ons and changes that aren't allowed in the cloud-hosted version.

Re: AWS S3 open source alternative written in Go

#78

Post by corobo »

Ixiaus wrote: post #47

Or, run Riak with their S3 compatibility layer. Riak is extremely stable and the work Basho has done to make a truly robust distributed database is significant. http://docs.basho.com/riak/cs/2.1.1/

There's also Skylable's SX Cluster if you use the libres3 daemon with it. Been using it for over a year with no problems. Set, forget, add more nodes when I need more disk.

Everyone's got their s3 of choice, always good to have more options on the table.

https://www.skylable.com/products/sx/

https://www.skylable.com/products/libres3/

Re: AWS S3 open source alternative written in Go

#79

Post by theanalyst »

viraptor wrote: post #76
Ixiaus wrote: post #47

Or, run Riak with their S3 compatibility layer. Riak is extremely stable and the work Basho has done to make a truly robust distributed database is significant. http://docs.basho.com/riak/cs/2.1.1/

Other alternatives: ceph - http://docs.ceph.com/docs/master/radosgw/s3/ swift - https://wiki.openstack.org/wiki/Swift/APIFeatureComparison#A...

Also ceph (& swift) are known to scale well in prod. clusters with over 30+ PB of data (at least looking at CERN's cluster) and the latest version of RGW does support geographic redundancy for S3 like apis

Re: AWS S3 open source alternative written in Go

#80

Post by corobo »

RubyPinch wrote: post #70
rsync wrote: post #56

Earlier quoted context omitted.

Current opinion is that "borg" is the holy grail of backup schemes ... it takes attic, which fixed all of the duplicity shortcomings, and improved on that ... [1] We[2][3] tend to agree with that. One reason it might not work for you is that we are an order of magnitude more expensive than B2, so perhaps that's a better bet for you. On the other hand, $7.20 per year for our smallest borg account is almost as close to…

from [3] > If you're not sure what this means, our product is Not For You. Please don't do that, its childish and unimpressive.

There's no support for that service. Makes sense to ward people off who might need support at the headline.
Post reply on HN