Transactions and Concurrency Control are very of paramount importance when it comes to enterprise systems data integrity.
However, this topic is very tough since you have to understand the inner workings of the database system, its concurrency control design choices (e.g. 2PL, MVCC), transaction isolation levels and locking schemes.
In this presentation, I'm going to explain what data anomalies can happen depending on the transaction isolation level, with references to Oracle, SQL Server, PostgreSQL, and MySQL.
I will also demonstrate that database transactions are not enough, especially for multirequest web flows. For this reason, I'm going to present multiple applicationlevel transaction patterns based on both optimistic and pessimistic locking mechanisms.
Last, I'm going to talk about Concurrency Control strategies used in the Hibernate secondlevel caching mechanism, which can boost performance without compromising strong consistency.