5 ms·
In case of my previous employer it led to incredibly complicated encryption system. It took couple years to maybe implement in 10% of the system. Deleting any o
by jeff_vader 5y ago
In case of my previous employer it led to incredibly complicated encryption system. It took couple years to maybe implement in 10% of the system. Deleting any old data was rejected.
- hinkley 5y agoI wonder sometimes if it would help if we collectively watched more anti-hoarding shows, in order to see how the consultants convince their customers they can get rid of stuff.
- mro_name 5y agohumans started their first 300k years as nomads – storing was just impossible and decrufing happened by itself when moving along. So maybe that's why we're not good at it yet.
- hinkley 5y agoBeing a renter definitely kept me lighter for a long time. When you have to box things up over and over you find that the physical and mental energy around keeping it aren’t adding up. I wonder if migrating from cloud to cloud would simulate this experience.
- travisgriggs 5y agoTwo space garbage collector in action right there. Maybe all things software need a "move it or lose it" impetus. Features in apps, old data, you name it. If you've gotta keep transferring/translating it, it would definitely pare things down.
- mro_name 5y agomaybe reuse is inferior to re-implement. Moderately re-inventing wheels may be beneficial. What may be a threshold?
- Bayart 5y agoBeing a renter just taught me to batch my $STUFF I/O to minimize read-writes to disk and maximize available low-latency space. ie. fill my bags to the brim with shit I didn't plan using whenever I'd go to my parents'.
- fomine3 5y agoAlso hoarding digital data is far easier than real. I wish I could have grep on real space.
- stingraycharles 5y agoHow is encryption compliant? I’ve implemented GDPR data infrastructures twice now, and as far as I’m aware, the only way to be compliant with encryption is when you throw the decryption key away.
- aeyes 5y agoSometimes it might be a single field in a 1MB nested structure that you have to remove. So it gets encrypted when the whole structure gets stored and when the field is to be deleted you just throw away the key instead of modifying the entire 1MB just to remove a few kB.
- dylan604 5y agoIf you're comparing gov't regulations to delete data to saving a few KB, then I think you're looking at this wrong.
- viraptor 5y agoIt's few KB per-record. In practice when schemes like that are applied, it means "in total we can remove this key and not rewrite 10M rows across 3 data stores which itself would cost $$$ and make the database and incremental backups cry".
- ByteJockey 5y agoBingo. We did a similar thing except replacing the values with a UUID and storing the pair in a lookup table somewhere. Delete that row and none of the rest of the data is able to be tied back to a human being. Bonus, most people didn't need that data, and it was no longer given out to everyone who grabbed the entire dataset.
- spelunker 5y agoAs mentioned, encrypt something and throw a way the key, often called "crypto shredding".