Effective Transactions Management with Spring
summary
Claims that the Lost update must never occur and shows concrete Spring code using Spring Data JPA, Hibernate, Lombok and JUnit tests. A demo app on GitHub runs debug tests that show values evolving 180 → 190 → 200 under different isolation settings: repeatable read blocks a concurrent writer, read committed allows non‑repeatable reads, and serializable serializes transactions (size examples 5 → 6 → 7), proving the behaviors and performance tradeoffs.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:04What is a transaction
- 7:25Transaction problems
- 8:29Isolation levels explained
- 14:21Choosing isolation levels
- 14:44Demo setup
- 20:17Testing transactions
- 32:16Key takeaways
related talks
42mEffective transaction management with Spring
01h 17mUsing @Transactional Like a Pro
41mTransactions: myths, surprises and opportunities
01h 01mLost in transaction Strategies to manage consistency in distributed systems
58mMaintain Social Distance this Spring
43mBeing Transactional in 2019 — What Does That Actually Mean?
49mPerformance oriented Spring Data JPA & Hibernate
44mPerformance oriented Spring Data JPA & Hibernate