Actually transactions can be a secomd-layer safety-net for single-responsibility writers to ensure rollback on eg restarts and consistency on loadbalancer redecisions without having much of an impact on performance, and data integrity is usually quite important.
I get that this is a joke, but…
… ackshually it should almost never be a transaction only when there’s absolutely no other option, because transactions kill your performance.
Actually transactions can be a secomd-layer safety-net for single-responsibility writers to ensure rollback on eg restarts and consistency on loadbalancer redecisions without having much of an impact on performance, and data integrity is usually quite important.
Unless you’re using Firebird (3) in which not using transactions kills your performance