I wouldn’t really agree with incremental migrations being rotten. Having a set of homegrown scripts would, in my opinion, be a worse approach than having a real tool for such a job will make tracking those changes easier. I’ve had to deal with a similar situation myself, before, so hopefully I can share some of … Read more
There is an approach to designing systems with an idea of never deleting or mutating data called Event Sourcing. Basically, the idea is to store events (or facts) that change the system state, instead of snapshots of the state. The history of events can be replayed later on to produce a certain purpose-specific projection of … Read more
The first big question when diving in to this is “how do you want to store changesets”? Diffs? Whole record copies? My personal approach would be to store diffs. Because the display of these diffs is really a special action, I would put the diffs in a different “history” collection. I would use the different … Read more