Transaction management with @Transactional in Spring Boot - Performance & Optimization

Performance: Transaction management with @Transactional

MEDIUM IMPACT

This affects backend transaction handling speed and resource locking, indirectly impacting frontend responsiveness and user experience.

Managing database transactions in a Spring Boot service

Spring Boot

@Transactional
public void updateData() {
  repository.save(entity1);
  repository.save(entity2);
  // atomic commit or rollback
}

Wraps all DB operations in one transaction, reducing commits and locks, ensuring atomicity and faster completion.

📈 Performance GainSingle DB commit reduces lock time and improves interaction responsiveness.

Managing database transactions in a Spring Boot service

Spring Boot

public void updateData() {
  // multiple DB calls without @Transactional
  repository.save(entity1);
  repository.save(entity2);
  // no rollback on failure
}

Without @Transactional, partial updates can occur, causing inconsistent data and multiple separate DB commits that increase latency and lock time.

📉 Performance CostTriggers multiple DB commits and locks, increasing response time and blocking resources longer.

Performance Comparison

Pattern	DB Operations	Locks Held	Response Delay	Verdict
No @Transactional with multiple DB calls	Multiple separate calls	Longer lock duration	Higher delay due to multiple commits	[X] Bad
Single @Transactional wrapping DB calls	Single atomic call	Shorter lock duration	Lower delay with one commit	[OK] Good

Rendering Pipeline

While @Transactional runs on the server side, its efficiency affects how quickly the server responds to frontend requests, impacting the browser's ability to paint updated content and respond to user input.

→Server Processing

→Network Response

→Browser Paint

⚠️ BottleneckServer Processing due to database locks and transaction overhead

Core Web Vital Affected

INP

This affects backend transaction handling speed and resource locking, indirectly impacting frontend responsiveness and user experience.

Optimization Tips

1Use @Transactional to wrap related DB operations for atomic commits.

2Avoid long-running transactions to reduce database lock contention.

3Monitor backend response times to detect transaction bottlenecks.

Performance Quiz - 3 Questions

How does using @Transactional affect backend performance?

A It groups DB operations into one transaction, reducing commits and locks.

B It increases the number of DB commits to improve speed.

C It delays all DB operations until the user refreshes the page.

D It disables database locking to speed up queries.

DevTools: Network

How to check: Open DevTools, go to Network tab, observe backend API call durations and response times during DB updates.

What to look for: Look for long server response times indicating slow transaction processing or multiple round trips.

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