Using explicit transactions

Transactions define a boundary: anything (and everything) inside a transaction is either guaranteed to fail or succeed. Imagine a bank transfer from one bank to another. If you think of the steps involved, they are as follows:

  1. Some amount is withdrawn from a bank account.
  2. The same amount is deposited in another bank account.

One cannot exist without the other: both actions must either occur or neither of them can occur in isolation.

Transactions have what is commonly referred to as the ACID properties. This acronym is explained in the following sections.


The execution of any transaction should either have the full intended effect or no effect at all. The results should be either complete (commit), or nothing should ...

Get Entity Framework Core Cookbook - Second Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.