⚡ CrackLab/Databases Mastery
RoadmapQuizFlashcards🔍
Databases Mastery›Transaction Mastery›Persistence Context & Dirty Checking

⚖️ Transaction Mastery

  • 1What Is a Transaction?
  • 2Atomicity
  • 3Consistency
  • 4Isolation & Anomalies
  • 5Durability
  • 6SQL Transaction Control
  • 7Locking, MVCC & Deadlocks
  • 8@Transactional Fundamentals
  • 9Propagation & Isolation in Spring
  • 10Transaction Manager Internals
  • 11Programmatic, Reactive & Nested Transactions
  • 12Persistence Context & Dirty Checking
  • 13Entity Lifecycle, Caching & Transaction Boundaries
  • 14MongoDB Transactions
  • 15Why Local Transactions Fail
  • 16Two-Phase Commit (2PC)
  • 17Saga Pattern
  • 18Outbox, Inbox & CDC
  • 19Kafka Transactions & Exactly-Once Semantics
  • 20System Design with Transactions
  • 21Production Engineering
  • 22Capstone — A Fault-Tolerant Order-Payment System
intermediate~2h

Persistence Context & Dirty Checking

You've never called.save() after modifying a loaded entity, and it still worked. This chapter is why — and it's one of the most-asked internals questions in mid-to-senior Java interviews.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Databases Mastery library.

Persistence Context & Dirty Checking

Next Step

Continue to Entity Lifecycle, Caching & Transaction Boundaries →← Back to all Transaction Mastery chapters