Prod backups in staging? Why not
summary
A runnable Laravel 9.x service launched from a Bitbucket pipeline that builds a Kubernetes pod to dump a production MySQL database, anonymize data using information_schema metadata and per-table mutators, and import the anonymized dump into a staging database. Configuration specifies source/destination, columns and custom mutators; a ~1 GB test takes about 40–50 minutes end-to-end, and the pod plus local DB are destroyed after the run. The uploader states the anonymization follows GDPR-safe practices used in Jobtech.
AI-written summary · about
chapters (10)
- 0:00Data anonymization intro
- 2:16Microservice needs
- 8:04MySQL Information Schema
- 12:24System structure
- 21:42Anonymization steps
- 29:57Staging results
- 31:23Conclusion
- 32:04Q&A: schemas
- 34:35Q&A: prod anonymization
- 37:45Q&A: handling & performance
related talks
39mDatabase DevOps with Containers
59mTaking Care of Backups with Laravel
43m50 Shades of Backup
19mDeploying Laravel Applications with Bitbucket Pipelines
32mDon't Leave Your Production Data Lying Around: Anonymize It with DbToolsBundle!
35mTaking care of backups with Laravel
31mBobby Bouwmann :: Surviving Large Applications
51mMySQL Backups