-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this project still alive ? #4
Comments
Is nimbus.io even stil alive itself ? Last twitter was on 10 Apr 2013.... |
Was wondering the same thing, a few years later. Hope it's just moved 😇 |
I'm sorry to say that Nimbus.io is no longer maintained by SpiderOak. At the time Nimbus.io was created, there were no reliable object stores that use erasure coding to achieve redundancy instead of using replication. That was the appeal for the system at SpiderOak: we store many petabytes of data, and replication has far higher overhead in terms of total storage required. However now other open source projects support erasure coding: e.g. Ceph http://docs.ceph.com/docs/master/rados/operations/erasure-code/ and Minio https://github.com/minio/minio/tree/master/docs/erasure Cheers! |
Hi,
Interested in nimbus but a little worried that no contribution has been made in almost 10 months and there are 2 issues left with no comment what so ever...
Is nimbus.io actually running on this open source project at all ?
The text was updated successfully, but these errors were encountered: