Are there any downsides to transactions?

Question

MySQL

Are there any downsides to using transactions in databases?

Answer 1

Directly from the introduction of transactions, nothing starts to work more slowly.
The slowdown can be from two things:
a) if transactions are used thoughtlessly, for example, the transaction is not completed at the moment when it should be completed according to the business logic - accordingly, the records are blocked for an extra time, another thread cannot change them.
b) if strict settings for saving to disk are set
Michael : because writing to disk is an expensive procedure. But in general, the need for this depends on the business logic of the application itself and the required consistency.
It's one thing if you have financial data in a transaction, it's another thing if you make a conditional chat.

Answer 2

Real transactions must be immediately flushed to disk, for example, innodb performance drops by about 100-200 times with this setting