Architecture

Nimbus.IO has a parity-based storage system.


Nimbus.IO vs traditional distributed storage systems

Storage typeParity-basedReplication-based
ExamplesNimbus.IO, RAID6, Usenet BinariesGluster, MogileFS, Riak + Luwak, Amazon S3
Overhead
datum
25% overhead from parity200% overhead from copies
Consequences of the design
  • Data is striped with parity across 10 nodes
  • Supports greater throughput for large requests
  • Lower cost solution for cooler data
  • Data is copied to 3 nodes
  • Supports greater concurrency of small requests
  • Lower latency solution for warmer data

Both systems tolerate destruction of any 2 nodes without data loss.