Rate this article: not the finest
The article sort of explains what various RAID levels imply, whilst saying nothing about wtf erasure codes are. Is RAID now so old-fangled that it needs to be explained, whereas erasure codes are like DevOps, their value and implementation are self evident (preferably after a conference or two)?
In particular the article says nothing (that I could see) about the fact that an array rebuild could be bottlenecked in principle either by IO performance or (depending on implementation) by CPU performance.
My limited knowledge of erasure codes (about five minutes old, found in
http://www.computerweekly.com/feature/Erasure-coding-versus-RAID-as-a-data-protection-method )
suggests that erasure codes are quite possibly more likely to be CPUbound than their RAID equivalent (again, depending on implemenation).
Odd article.
Biting the hand that feeds IT
