A common problem is that you want to keep track of the number of certain things; and while creating or deleting things generally modifies different database rows for each thing, all the actions try to modify the same counter, so you get peformance problems, deadlocks and timeouts, sometimes even outages.
Examples include edit counts, category membership counts (T365303), change tag counts.
One solution is to move these changes to a job, but that introduces random delays (and occasionally the jobs getting lost) which can be a mild annoyance for editors who sometimes rely on these counts (e.g. edit counts can determine permissions; non-empty maintenance categories are sometimes used as calls-to-action for admins). It might be worth coming up with a generic mechanism that's easy to add to new individual use cases.