SLA for database writes
Currently we don't have any SLA/limitations on how many writes our application can perform. This has historically (and still does) lead to cases where some piece of the code for varying reasons decided it was a good idea to rewrite entire tables. This in turn puts a lot of pressure on vacuuming, increasing storage space (depending on the number of rows updated this can easily be GBs of data).
As a first line of defence against this we need some kind of SLA that says how many inserts, updates, deletes, etc you can perform in a given time frame per table. Whenever these SLAs are crossed the responsible teams should be notified. For example, issues would be the responsibility of the Discussion team.
I'm not sure how we'd act upon violating the SLA, but at least there should be some form of pressure to stick with the SLA.