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

+1 for Ceph. We're running several ~3.5 PB clusters in production. We've not taken advantage of the new RGW features in Jewel, but it works well as an object storage solution.

Don't forget:

manta - https://www.joyent.com/manta

CEPH is a volume service not an object storage service.

SWIFT is indeed analogous to S3.

Come on, I literally linked to a website describing "CEPH OBJECT GATEWAY S3 API"

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

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

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

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

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

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/

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?

There's also Pithos from Exoscale. Runs on top of Cassandra. Code is Clojure and open source. Http://Pithos.io

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.

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

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