2 ms·
> And the number of rows in the table, effectively bloating it for all time. Particularly in the case of growth oriented companies, if your user base is growin
by hinkley 3y ago
> And the number of rows in the table, effectively bloating it for all time.
Particularly in the case of growth oriented companies, if your user base is growing exponentially, then half of your records are less than a year old anyway. This bloat is not the problem you make it. And as I said elsewhere, a row that is tombstoned can be deleted offline at some cadence that doesn’t break your other workflows. For instance when nearly all of its siblings are also dead.
- hobs 3y agoUsers per second and rows per second are not really that strongly correlated - plenty of services create an excessive amount of noise for a fairly low amount of "real rows". You can push on devs to fix things like pointless logical updates but its really easy to have a rogue process create copies of your entire dataset each time it runs.