3 ms·
I like this idea but the article doesn't do a great job of spitting out why it's valuable. Consider a SAAS with 25,000 active customers and tons of structured
by michaelbuckbee 7y ago
I like this idea but the article doesn't do a great job of spitting out why it's valuable.
Consider a SAAS with 25,000 active customers and tons of structured (database) data.
You have a bunch of people that need to work on the dev system and the closer dev looks to prod the better you are.
- Contractors in another country
- A team working on basic compliance with GDPR and CCPA
- Sysadmin team trying to manage backups/restores
When the contractors pull a version of the DB it needs to not have any customer data (emails, addresses, etc.) so there's a process that wipes all those out and fills them in with fake data.
When the GDPR team gets a data deletion request ("Please delete all my data my email is X@y.com") on Monday and the Sysadmin team restores from a backup from Sunday what happens?
Right now both of these actions are one-off things done with a mish-mash of scripts, organizational knowledge, and half-remembered processes.
So wouldn't this be better with a service that could talk to your DB and you could fork out versions that "knew" the current DB structure, that you could mark as purged of sensitive data, that you could apply (and re-apply) transforms to for structure to data addition/removal.