What are the disadvantages of implementing transactions away from the database?

We know that there are some scenarios that require us to implement transactions in code, such as SqlTransaction/ TransactionScopein the .Net framework. Questions:

  • What are the overheads (other than speed)?
  • Would it be worse if we add more between the transaction and the database? If so, what are the overhead and overhead?
+3
source share
2 answers

We want transactions to be short, to start them as long as possible and to put an end to them as soon as possible. Otherwise, concurrency hurts, and we get more wait locks and deadlocks.

+1
source

.

, , - , .

0

Source: https://habr.com/ru/post/1767499/


All Articles