transaction

Configure Spring transaction propagation and isolation levels using the @Transactional annotation to define database transaction boundaries and ensure data integrity. This Skill provides rules for selecting appropriate propagation behaviors and isolation settings.

Spring @Transactional rollback fails during self-invocation because proxy-based AOP intercepts external calls. This Skill identifies common transaction pitfalls like self-invocation and external I/O within transactions, providing guidance to resolve them.

Spring routes read-only transactions to slave databases by checking the transaction read-only status via DataSource routing. This Skill explains how Master/Slave routing automatically directs read-heavy reporting queries to read replicas.

Use Spring transaction timeouts to limit execution duration and avoid external calls to prevent database connection exhaustion. This Skill provides guidance on handling external I/O within transactions and setting appropriate timeout constraints.

The default propagation level for Spring @Transactional is REQUIRED, joining an existing transaction or starting a new one. This Skill helps you understand default propagation behaviors to ensure critical operations are atomic and consistent.