> So immutable records only makes business sense in databases too small to benefit from immutable records
My claim is that discarding historical data is an optimization. Its an optimization that should be off by default and turned on when needed. Archiving and compacting history should be something you do only need to do when your database size gets out of control.
For small databases there's no reason to throw away historical records at all - and having an immutable log of records and updates should be the default.
My claim is that discarding historical data is an optimization. Its an optimization that should be off by default and turned on when needed. Archiving and compacting history should be something you do only need to do when your database size gets out of control.
For small databases there's no reason to throw away historical records at all - and having an immutable log of records and updates should be the default.