It has been a long time since I have been involved in Storj. I just popped back to have a look at how it is doing and to potentially start getting involved again (A long time back I wrote the first Java client for Storj when it was new).
Having a look through the site I saw a couple of things worth mentioning.
On this page: Backups
Files are downloaded on demand using multi-layered parallelism (pulling from multiple Nodes around the globe)—this provides low latency, and higher throughput ensuring higher RTO and RPO.
RTO = Recovery Time Objective, the time it takes to restore service
RPO = Recovery Point Objective, a measurement in time of how much data you can accept to lose in the case of a disaster.
These are not things you would want to ensure are higher. You want them to be lower. Higher means you lose more data and it takes longer to recover.
Storj DCS lowers storage and egress costs by at least 80%, and significantly reduces TCO
TCO = Total Cost of Ownership. It’s a bad thing, again so we want it low. This is correct on this page. However, go to the pricing page here and you get the statement:
Storing more than 25TB? You can save at least 80% and maximize TCO when you store on the decentralized cloud
No thanks! I don’t want to maximise my total cost of ownership!