Let’s charitably say you can run your app with a 1GB cut down snapshot of production.
You’re going to do what, save a snapshot of the database for every commit? Every schema migration?
…and then provision that up in a running database server… which is notoriously not container friendly…
? It doesn’t sound very plausible to me.
Our database is ~1TB, and the app runs with maybe a 10GB cut down version of it, which is a pain in the ass to deal with, just for example, for local dev environments.
I agree with the parent post; it’s cute, but I can’t imagine historical per commit deployments being useful for me, honestly.
Plenty of apps can run from an empty database, if the data storage is focused on resources you, the user, have created for yourself.
But I imagine that people with their heads in the future are imagining you'll use one of these new database startups (the names escape me) to manage snapshots, seeding from anonymised production data, etc.
Most of our effort is in user experience and post processing.
It would be nice to compare the experience of todays version with one from 6 months or 1 year ago for certain components.
We do already have a historical design storyboard but seeing it with live data would be more useful.
Just fire up a fresh DB with some sensible default fixtures.
Or pause an integration test mid-way.
Or call some factories from the REPL.
The last thing in the world I want to do development with is production data. Production data is the data of last resort when nothing else can repro.