Transform your development workflow with thin cloning
summary
Thin cloning reproduces production data and schema so developers get writable copies that behave like prod for debugging and performance work it uses copy‑on‑write storage and services such as DBLab Engine (physical), Aurora cloning and Zeta with logical replication and tools like PGBackRest and PG stream and the team’s db_clone script returns a usable Rails connection in 3 seconds so developers can reproduce partitioning bugs, catch slow query plans and run safe explain analyze on clones it requires same‑region placement for low latency and either access controls or logical + anonymization for PII.
AI-written summary · about
chapters (8)
- 0:00Introduction and motivation
- 7:47Development data struggles
- 15:29Thin cloning explained
- 22:53Schema and performance fixes
- 29:30Zero-to-one product benefits
- 32:39Challenges and trade-offs
- 37:16PII and compliance solutions
- 39:23Closing thoughts and Q&A
related talks
17mA Laboratory for Databases
38mPerforming Databases Migrations Without Overtime
47mEfficiency up, failed releases down; compliant production data for your test and dev environments- 47mEfficiency up, failed releases down; compliant production data for your test and dev environments
37mTransforming Test Data Delivery for Shift Left Automation (Closing Keynote)
25mBig Bad World of Postgres Dev Environments
48mDevOps Discovery: Navigating the Database Landscape- 48mDevOps Discovery: Navigating the Database Landscape