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

111–120 of 139 posts

Re: AWS S3 open source alternative written in Go

#111

Post by unlocksmith »

merb wrote: post #74
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.

Minio is deliberately designed this way. Cloud native applications require strict multitenancy. Minio's approach is to build just enough to meet a single tenant's requirement. Deploy one minio server per tenant or user or customer .. whichever fits you the best. This will allow you to upgrade, customize or bug fix in isolation. To replicate for HA, use "mc mirror -watch SOURCE TARGET" command to pair them up. If you have multiple drives (JBOD), you can eliminate RAID or ZFS and use Minio's erasure code to pool them up. Distributed version is also in testing at the moment. It should be out in a month.

Re: AWS S3 open source alternative written in Go

#112

Post by helper »

y4m4b4 wrote: post #51
helper wrote: post #50

How easy is it to embed this into go tests? Right now I use goamz/s3test for that, but it has a lot of limitations.

Quite easy actually you can look at https://github.com/restic/restic/blob/master/run_integration...

I don't want to run it in an external process, I want to run it in a goroutine.

Re: AWS S3 open source alternative written in Go

#113

Post by takeda »

killbrad wrote: post #107
breakingcups wrote: post #77

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.

but then voiding the argument that was stated initially i.e. no one needs to maintain it and be on call for it

Re: AWS S3 open source alternative written in Go

#114

Post by jdboyd »

Natales wrote: post #106
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/

+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 dae…

Considering how many serious deployments still use non-clustered NASs, a single node object store seems equally reasonable.

Re: AWS S3 open source alternative written in Go

#115

Post by owyn »

Natales wrote: post #106
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/

+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 dae…

That sounds pretty nice. If it works does it need new features? :)

Re: AWS S3 open source alternative written in Go

#116

Post by dc2447 »

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/

Dont you have to pay for an enterprise licence if you want multi region/datacentre/AZ?

Re: AWS S3 open source alternative written in Go

#117

Post by dc2447 »

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...

CEPH is a volume service not an object storage service.

SWIFT is indeed analogous to S3.

Re: AWS S3 open source alternative written in Go

#118

Post by XorNot »

dc2447 wrote: post #117
viraptor wrote: post #76

Earlier quoted context omitted.

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

CEPH is a volume service not an object storage service. SWIFT is indeed analogous to S3.

Ceph is object storage first. The volume service is implemented on top of that.

Re: AWS S3 open source alternative written in Go

#119

Post by mrweasel »

beastman82 wrote: post #102

written in Go - Does this matter?

Yes and no, if you're in the market for an S3 clone, but want to be able to add features, fix bug or hack on it in some way, it nice to know which language it's being developed in.

As you can tell from the other comments, there's plenty of alternatives to pick from, and if you're going to dive in to the code yourself the language may be a deciding factors.

Re: AWS S3 open source alternative written in Go

#120

Post by merb »

unlocksmith wrote: post #111
merb wrote: post #74

Earlier quoted context omitted.

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.

Minio is deliberately designed this way. Cloud native applications require strict multitenancy. Minio's approach is to build just enough to meet a single tenant's requirement. Deploy one minio server per tenant or user or customer .. whichever fits you the best. This will allow you to upgrade, customize or bug fix in isolation. To replicate for HA, use "mc mirror -watch SOURCE TARGET" command to pair them up. If you…

I know and that. And that's why I find minio interesting. Start with a single node. Raise up to 16.
Post reply on HN