EF Core or Dapper? A deliberate split instead of one ORM everywhere
Use EF Core where you change data and Dapper where you read it for a screen or a report. Here is why the split works, with runnable code that shares one connection.
.NET
Optimistic vs pessimistic concurrency in EF Core, explained with a wallet balance
Two withdrawals read the same balance and both succeed: that's a race condition. Three ways to stop it in EF Core (rowversion, an atomic update, and a row lock) and when to use each.