Live data from Hacker News

AWS S3 open source alternative written in Go

minio.io

131–139 of 139 posts

Re: AWS S3 open source alternative written in Go

#131
post #80

Earlier quoted context omitted.

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.

Just to be clear, there is no support for the deeply discounted borg/attic accounts at rsync.net.

Regular rsync.net accounts have full, unlimited support provided by a US-based engineer. As in, an honest to god unix engineer. Sometimes, but rarely, me.

Re: AWS S3 open source alternative written in Go

#132
post #128

Earlier quoted context omitted.

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

Another interesting project written in Erlang is LeoFS: http://leo-project.net/leofs/

Worth adding that LeoFS is being used in production by Rakuten for years now. Still not a widely known project for some reason.

http://www.slideshare.net/rakutentech/scaling-and-high-perfo...

Re: AWS S3 open source alternative written in Go

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

This is true if you are first and foremost a company that provides technology to other customers, and in that case, you

a) have a very competent dev and ops team b) have a business where you are the provider of an SLA.

For many companies with 5K+ employees, they are already distributed, already have multiple data centers, have workers all over the globe, and, when they are not primarily in the IT delivery business, tend to have IT departments that have limited budgets, lack of training and poor organizational awareness.

This leads to poor security practice, poor cost analysis, and long/nonexistent upgrade cycles on many behind-the-scenes workloads.

You are of course right, there are many diverse reasons to be on-prem, but at some point, many of those reasons go away with sufficient size and differing priorities. Things change when a company's business involves the consumption of IT services, rather than the delivery of IT services.

Re: AWS S3 open source alternative written in Go

#134
post #116
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?

[deleted]

Re: AWS S3 open source alternative written in Go

#135

Earlier quoted context omitted.

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

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.

I was actually thinking of using a custom network, not truly IPFS.

Re: AWS S3 open source alternative written in Go

#136

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.

It is important, because you will not find any Go-developers on the market, so if you are serious about using it then think twice ;)

Re: AWS S3 open source alternative written in Go

#138
post #112
post #51

Earlier quoted context omitted.

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.

For that you can just do

```

package main

import minio "github.com/minio/minio/cmd"

func main() {

        go minio.Main()

        ... do your stuff ...
}

```

Re: AWS S3 open source alternative written in Go

#139

couldn't find at a glance wheter it has the same read after write issue of s3, or in general what the consistency is. also, failure and backup modes.

Minio server provides read-after-write consistency. For fault-tolerance, * protection against failed disks, you could deploy Minio erasure code setup. ref: https://docs.minio.io/docs/minio-erasure-code-quickstart-gui...

* Minio erasure code setup also provides protection against "bit-rot".

Post reply on HN