Transaction management with @Transactional in Spring Boot

Introduction

Transaction management helps keep your data safe and consistent. The @Transactional annotation makes sure a group of actions either all happen or none happen.

When saving multiple related records to a database and you want all to succeed or all to fail.

When updating several tables and you want to avoid partial updates.

When deleting data that depends on other data and you want to keep the database consistent.

When calling multiple database operations in one method and you want them treated as one unit.

When you want to automatically rollback changes if an error happens during a process.

Syntax

Spring Boot

@Transactional
public void methodName() {
    // database operations
}

Place @Transactional above methods or classes to manage transactions.

By default, if an exception occurs, the transaction rolls back.

Examples

This method saves a user inside a transaction.

Spring Boot

@Transactional
public void saveUser(User user) {
    userRepository.save(user);
}

This method reads data without allowing changes, improving performance.

Spring Boot

@Transactional(readOnly = true)
public User findUser(Long id) {
    return userRepository.findById(id).orElse(null);
}

This method rolls back the transaction for any exception, checked or unchecked.

Spring Boot

@Transactional(rollbackFor = Exception.class)
public void updateData() throws Exception {
    // multiple database updates
}

Sample Program

This service simulates a money transfer. If the amount is over 1000, it throws an error and rolls back the transaction, so no changes happen.

Spring Boot

import org.springframework.stereotype.Service;
import org.springframework.transaction.annotation.Transactional;
import java.util.ArrayList;
import java.util.List;

@Service
public class BankService {

    private List<String> transactions = new ArrayList<>();

    @Transactional
    public void transferMoney(String fromAccount, String toAccount, int amount) {
        transactions.add("Withdraw " + amount + " from " + fromAccount);
        if (amount > 1000) {
            throw new RuntimeException("Amount too large, rollback transaction");
        }
        transactions.add("Deposit " + amount + " to " + toAccount);
    }

    public List<String> getTransactions() {
        return transactions;
    }
}

Important Notes

Use @Transactional on public methods only for it to work properly.

By default, only unchecked exceptions (RuntimeException) cause rollback.

Transactions help keep your data safe when multiple steps must all succeed together.

Summary

@Transactional groups database actions so they all succeed or fail together.

It helps keep data consistent and safe from partial changes.

Use it on methods that do multiple related database operations.

Practice

1. What is the main purpose of using @Transactional in a Spring Boot application?

easy

A. To ensure multiple database operations are executed as a single unit and rollback on failure

B. To speed up database queries by caching results

C. To automatically generate database schema from entities

D. To log all database queries for debugging

Solution

1. Step 1: Understand the role of @Transactional

   @Transactional groups multiple database operations so they succeed or fail together.

2. Step 2: Identify the effect on data consistency

   If any operation fails, all changes are rolled back to keep data correct.

3. Final Answer:

   To ensure multiple database operations are executed as a single unit and rollback on failure -> Option A

4. Quick Check:

   @Transactional = atomic database actions [OK]

Hint: Think: all-or-nothing for database changes [OK]

Common Mistakes:

• Confusing @Transactional with caching or logging
• Thinking it speeds up queries
• Assuming it auto-generates schema

2. Which of the following is the correct way to apply @Transactional to a method in a Spring Boot service class?

easy

A. @Transactional public void updateData() { ... }

B. public @Transactional void updateData() { ... }

C. public void updateData() @Transactional { ... }

D. public void updateData() { @Transactional ... }

Solution

1. Step 1: Recall correct annotation placement

   Annotations like @Transactional go before the method signature.

2. Step 2: Check each option's syntax

   @Transactional public void updateData() { ... } places @Transactional correctly before the method declaration.

3. Final Answer:

   @Transactional public void updateData() { ... } -> Option A

4. Quick Check:

   Annotation before method = correct syntax [OK]

Hint: Annotations always go before method signature [OK]

Common Mistakes:

• Placing annotation inside method body
• Putting annotation after method signature
• Using annotation as a modifier keyword

3. Consider this Spring Boot service method annotated with @Transactional:

@Transactional
public void saveUserAndAccount(User user, Account account) {
    userRepository.save(user);
    accountRepository.save(account);
    if(account.getBalance() < 0) {
        throw new RuntimeException("Negative balance not allowed");
    }
}

What happens if account.getBalance() < 0 is true during execution?

medium

A. An error is logged but changes are committed

B. Only the user is saved, account save is rolled back

C. Both user and account are saved to the database

D. Neither user nor account is saved; transaction rolls back

Solution

1. Step 1: Understand rollback behavior of @Transactional

   By default, RuntimeExceptions cause the transaction to rollback all changes.

2. Step 2: Analyze the exception thrown

   The method throws RuntimeException if balance is negative, triggering rollback.

3. Final Answer:

   Neither user nor account is saved; transaction rolls back -> Option D

4. Quick Check:

   RuntimeException triggers rollback = no data saved [OK]

Hint: Exception inside @Transactional rolls back all changes [OK]

Common Mistakes:

• Assuming partial saves happen
• Thinking only last save rolls back
• Ignoring exception effect on transaction

4. Given this method in a Spring Boot service:

@Transactional
public void updateRecords() {
    recordRepository.updateA();
    recordRepository.updateB();
    // Missing exception handling
}

If updateB() throws a checked exception (not RuntimeException), what will happen to the transaction?

medium

A. Transaction will rollback automatically

B. Transaction will commit despite the exception

C. Transaction will rollback only if exception is caught and rethrown as RuntimeException

D. Transaction will pause until exception is handled

Solution

1. Step 1: Recall default rollback rules of @Transactional

   By default, only unchecked exceptions (RuntimeException) cause rollback.

2. Step 2: Analyze checked exception behavior

   Checked exceptions do not trigger rollback unless configured or rethrown as RuntimeException.

3. Final Answer:

   Transaction will commit despite the exception -> Option B

4. Quick Check:

   Checked exceptions do not rollback by default [OK]

Hint: Only RuntimeExceptions rollback by default [OK]

Common Mistakes:

• Assuming all exceptions cause rollback
• Not knowing difference between checked and unchecked exceptions
• Expecting rollback without configuration

5. You have a Spring Boot service with two methods:

public void outerMethod() {
    innerMethod();
}

@Transactional
public void innerMethod() {
    // database updates
    if(someCondition) throw new RuntimeException();
}

If outerMethod() is called, will the transaction rollback if innerMethod() throws the exception? Assume default proxy-based Spring transaction management.

hard

A. Yes, but only if outerMethod is also annotated with @Transactional

B. Yes, transaction rolls back because innerMethod is @Transactional

C. No, transaction does not rollback because outerMethod is not @Transactional and calls innerMethod internally

D. No, because RuntimeException does not trigger rollback in this case

Solution

1. Step 1: Understand Spring proxy behavior for @Transactional

   Spring uses proxies, so self-invocation (method calling another in same class) bypasses proxy and ignores @Transactional.

2. Step 2: Analyze effect on transaction rollback

   Since outerMethod calls innerMethod directly, @Transactional on innerMethod is ignored, so no transaction starts and no rollback occurs.

3. Final Answer:

   No, transaction does not rollback because outerMethod is not @Transactional and calls innerMethod internally -> Option C

4. Quick Check:

   Self-call bypasses @Transactional proxy = no rollback [OK]

Hint: Self-calls ignore @Transactional proxy, no transaction started [OK]

Common Mistakes:

• Assuming @Transactional always works on internal calls
• Thinking RuntimeException always triggers rollback here
• Not knowing Spring proxy limitations