4 ms·
I wonder if they discuss that and actually write down calculations
by agumonkey 6y ago
I wonder if they discuss that and actually write down calculations
- vidarh 6y agoI've designed a storage system for an image storage app for a client, and I had an extensive spreadsheet with the cost and risks of various combinations of erasure coding and data centres, as well as other mitigations. So yes. But this data loss highlights that all too often it ends there, with calculating the risk of loss due to hardware or data centre failures. You need to also do the same in terms assessing how you design your software, and what processes you put in place to mitigate risks. In this case it was the software system design that failed: They allowed the system access to modify long term stored data, when really the system ought to have been designed to allow "write once unless the user has convinced us that they really, really want the data destroyed, in which case keep a backup for a limited time" type design. A lot of software fails in that respect. The moment your internal API's allow modification of data, you risk catastrophic loss, as Canon found out, and you really ought to have strategies for mitigation of that.
- agumonkey 6y agoBut was this framed as easy business from gambling with users artefacts ? or just the usual "shit happens" preliminary thinking ?
- vidarh 6y agoI'd guess in this case nobody had thought about it as a real risk. People are often woefully unaware of the risks of accidental effects of unnecessary privileged.