There are many questions and responses on database triggers, however I have not found any that touch on network performance specifically, in the matter of benefits (or otherwise) of triggers.
I have this case:
Table A has rows that are data heavy (1-2 KB of JSON data). When one of the fields (status) is updated, the entire record has to be moved to another table (archive) and deleted from Table A. More than one row can be updated at a time.
Without getting into the merits of the design of the archive table, I have implemented this in a trigger ('after UPDATE' on Table A, copy record and the delete) - my logic being that there will not be any need for the data to be sent to the application (it is an app, with the dB on the cloud) and back again.
I believe this will improve end user experience, reduce network traffic, and de-risk issues with poor networks.
Are triggers still an 'avoid - these are bad'?