Skip to content
javabypankaj
HomeLibraryPopularCommunity
08
Transactions
10 topics · 32 questions
1@Transactional Basics0/772Declarative vs Programmatic0/223Isolation Levels & MVCC0/334Transaction Propagation0/445Rollback Rules & Pitfalls0/556Deadlocks & Locking0/227Events & Transaction Callbacks0/38Multiple DataSources0/229Distributed Transactions & Saga0/2210Transaction Internals0/22
1@Transactional Basics72Declarative vs Programmatic23Isolation Levels & MVCC34Transaction Propagation45Rollback Rules & Pitfalls56Deadlocks & Locking27Events & Transaction Callbacks38Multiple DataSources29Distributed Transactions & Saga210Transaction Internals2
10 topics32 Qs0%
01Core Java17002OOP3203Collections6704Exception Handling2805Concurrency & Multithreading12706Java Streams, Lambda & Functional Programming32807Spring & Spring Boot2608Transactions3209JPA & Hibernate6910Microservices19411Kafka & Messaging9112DevOps, CI/CD & Tooling13313Database & SQL14114REST API & Web4015Design Patterns & LLD5716Advanced Java7117Coding Problems: DSA49218AWS & Cloud4119Data Engineering19420QA, Testing & SDET4121System Design3522Security2023Behavioral / HR: STAR Method37
10Topics
32Questions
0%Complete
7 of 10 topics
Topics
1@Transactional Basics0/772Declarative vs Programmatic0/223Isolation Levels & MVCC0/334Transaction Propagation0/445Rollback Rules & Pitfalls0/556Deadlocks & Locking0/22
7Events & Transaction Callbacks0/33
8Multiple DataSources0/229Distributed Transactions & Saga0/2210Transaction Internals0/22

Events & Transaction Callbacks

Transactions·Topic 7 of 10·3 questions
Q1What is @TransactionalEventListener?

@TransactionalEventListener ties an event handler to the transaction outcome so side effects like SMS or email fire only when the transaction truly commits, preventing false confirmations.

Read Answer
Q2What is readOnly optimization and @TransactionalEventListener phases?

readOnly=true skips Hibernate dirty-checking and hints replica routing for read-heavy queries, while @TransactionalEventListener phases let you fire side effects at the right moment in the transaction lifecycle.

Read Answer
Q3What are TransactionSynchronization callbacks?

TransactionSynchronization is a Spring callback interface that lets you hook custom logic into the lifecycle of the current transaction, running the right side effect at the right moment: notify only after commit, clean up always after completion.

Read Answer
Previous · Topic 6Deadlocks & Locking2 questionsNext · Topic 8Multiple DataSources2 questions
javabypankaj© 2026 javabypankaj
PrivacyTerms
HomeSearchLibrary