Live data from Hacker News

AWS S3 open source alternative written in Go

minio.io

101–110 of 139 posts

Re: AWS S3 open source alternative written in Go

#101
I switched from Fake S3 [1] to Minio for local development. Fast and lightweight, good experience so far :)

Easy to setup with Vagrant, and linking / sharing the Minio shared folder to the host makes it quite convenient to quickly check the files without going to the UI [2].

[1] - https://github.com/jubos/fake-s3

[2] - It stores the files as-is in the local filesystem (files in folders, unchanged), as opposed to having it 'wrapped' like Fake S3 does.

Re: AWS S3 open source alternative written in Go

#104
post #96
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/

Ran Riak CS in production and had constant issues. It's not terrible but it's also not ideal. I would caution against anyone depending on it for mission critical systems. Many of the failure modes are undocumented.

Could you elaborate on some of the specific issues you ran into?

Re: AWS S3 open source alternative written in Go

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

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.

Re: AWS S3 open source alternative written in Go

#106
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/

+1 on RiakCS. They now call it RiakS2 for kicks. The scalability and reliability of their server is insane. You just can't beat Erlang software in that regard.

Unfortunately, Basho has been so successful with their TSDB and KV products that they have basically put S2 on maintenance mode. They are still "supporting" it, but no new features. I was hoping this Minio tool could do something similar, but with a single daemon is a single point of failure. Unacceptable for serious deployments.

Re: AWS S3 open source alternative written in Go

#107

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

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.

That's the Atlassian SaaS offering. You could still run it in any cloud yourself and get all the customizations you want.

Re: AWS S3 open source alternative written in Go

#108

Practical use case: - Spin up a bunch of droplets on DigitalOcean, because I want reliability, etc. - What's the best way to share drive space across these to create a single Minio storage volume, so if one DO node goes away I don't lose my stuff?

We are working on distributed minio https://github.com/minio/minio/tree/distributed The minio available today for production use can export single disk or aggregate multiple disks on the same machine using erasure coding. For this, if you want backup you can use github.com/minio/mc tool to mirror, more help here https://docs.minio.io/docs/minio-client-complete-guide#mirro...

I think this should be made clear on your site. I spent a good amount of time trying to figure out how to actually get this to be distributed, but the answer is - you don't. So it's only like S3 in interface, not in durability or availability.

Re: AWS S3 open source alternative written in Go

#109

Earlier quoted context omitted.

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.

That's the Atlassian SaaS offering. You could still run it in any cloud yourself and get all the customizations you want.

[deleted]
Post reply on HN