30 years of RDBMS and this topic is pretty much "uncharted territory" for the vast majority of back-end developers.
Transactions and Concurrency Control are 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 multi-request web flows. For this reason, I'm going to present multiple application-level transaction patterns based on both optimistic and pessimistic locking mechanisms.
Last, I'm going to talk about Concurrency Control strategies used in the Hibernate second-level caching mechanism, which can boost performance without compromising strong consistency.
Vlad Mihalcea
I am a Java Champion, working as a Developer Advocate for the Hibernate project.
I'm passionate about enterprise systems, data access frameworks, and distributed systems.
I wrote hundreds of articles about Hibernate on [my blog](vladmihalcea.com) and got gold badges for the Hibernate, Java, and JPA tags on [StackOverflow](stackoverflow.com/users/1025118/vlad-mihalcea).
I'm the author of [High-Performance Java Persistence](leanpub.com/high-performance-java-persistence).
Here, you can find a list of video presentations I gave at various Java conferences:
vladmihalcea.com/presentations/
