Service calling repository in Spring Boot - Performance & Optimization

Performance: Service calling repository

MEDIUM IMPACT

This pattern affects backend response time and indirectly impacts frontend load speed and interaction responsiveness.

Fetching data from database via service layer

Spring Boot

public class UserService {
    @Autowired
    private UserRepository userRepository;

    public List<User> getAllUsers() {
        List<Long> ids = getUserIds();
        return userRepository.findAllById(ids);
    }
}

Single repository call fetches all users at once, reducing database round trips.

📈 Performance GainSingle database query regardless of user count, significantly reducing response time.

Fetching data from database via service layer

Spring Boot

public class UserService {
    @Autowired
    private UserRepository userRepository;

    public List<User> getAllUsers() {
        List<User> users = new ArrayList<>();
        for (Long id : getUserIds()) {
            users.add(userRepository.findById(id).orElse(null));
        }
        return users;
    }
}

Multiple repository calls inside a loop cause many database queries, increasing latency.

📉 Performance CostTriggers N database queries for N users, increasing response time linearly.

Performance Comparison

Pattern	Database Queries	Backend Latency	Network Payload	Verdict
Multiple repository calls in loop	N queries for N items	High due to query overhead	Normal	[X] Bad
Single batch repository call	1 query for all items	Low due to reduced overhead	Normal	[OK] Good

Rendering Pipeline

Service calls to repository affect backend processing before data reaches frontend. Efficient calls reduce backend wait time, improving frontend rendering start.

→Backend Processing

→Network Transfer

→Frontend Rendering

⚠️ BottleneckBackend Processing due to multiple database queries

Core Web Vital Affected

INP

This pattern affects backend response time and indirectly impacts frontend load speed and interaction responsiveness.

Optimization Tips

1Avoid calling repository methods repeatedly inside loops in service layer.

2Use batch repository methods like findAllById to reduce database queries.

3Reducing backend latency improves frontend interaction responsiveness (INP).

Performance Quiz - 3 Questions

What is the main performance issue with calling repository methods inside a loop in a service?

A It reduces network payload size

B It increases frontend rendering time directly

C It causes multiple database queries increasing backend latency

D It improves caching automatically

DevTools: Network

How to check: Open DevTools Network tab, observe backend API response times and number of calls made to backend endpoints.

What to look for: Look for multiple backend calls or long response times indicating inefficient service-repository interaction.

Practice

1. What is the main role of a Service class in Spring Boot when it calls a Repository?

easy

A. To configure the database settings

B. To directly manage database connections

C. To replace the repository and perform SQL queries

D. To handle business logic and use the repository for data access

Solution

1. Step 1: Understand the role of Service

   The Service layer contains business logic and does not directly access the database.

2. Step 2: Understand the role of Repository

   The Repository handles data access and database operations.

3. Final Answer:

   To handle business logic and use the repository for data access -> Option D

4. Quick Check:

   Service handles logic, Repository handles data [OK]

Hint: Service = logic, Repository = data access [OK]

Common Mistakes:

• Thinking Service manages database connections
• Confusing Repository with Service responsibilities
• Assuming Service runs SQL queries directly

2. Which is the correct way to inject a repository into a service class in Spring Boot?

easy

A. Use @Autowired on a constructor parameter

B. Create a new repository instance inside the service method

C. Use new keyword to instantiate repository in service constructor

D. Declare repository as a static variable in the service

Solution

1. Step 1: Understand dependency injection in Spring Boot

   Spring Boot recommends constructor injection with @Autowired for better testability and immutability.

2. Step 2: Check options for repository injection

   Creating new instances manually or static variables break Spring's management and are not recommended.

3. Final Answer:

   Use @Autowired on a constructor parameter -> Option A

4. Quick Check:

   Constructor injection with @Autowired [OK]

Hint: Use @Autowired constructor injection for repositories [OK]

Common Mistakes:

• Manually creating repository instances
• Using static variables for repository
• Not using Spring's dependency injection

3. Given this service code snippet, what will getUserName(1) return if the repository finds a user with name "Alice"?

public class UserService {
  private final UserRepository userRepository;

  public UserService(UserRepository userRepository) {
    this.userRepository = userRepository;
  }

  public String getUserName(int id) {
    return userRepository.findById(id).map(User::getName).orElse("Unknown");
  }
}

medium

A. null

B. "Unknown"

C. "Alice"

D. Throws NullPointerException

Solution

1. Step 1: Understand repository method behavior

   findById(id) returns an Optional containing the User if found.

2. Step 2: Analyze service method logic

   The method maps the User to its name or returns "Unknown" if no user is found.

3. Final Answer:

   "Alice" -> Option C

4. Quick Check:

   User found returns name, else "Unknown" [OK]

Hint: Optional.map returns value or default [OK]

Common Mistakes:

• Assuming null is returned instead of default
• Expecting exception when user not found
• Confusing Optional usage

4. What is wrong with this service code that calls a repository?

@Service
public class ProductService {
  private ProductRepository productRepository;

  public void saveProduct(Product product) {
    productRepository.save(product);
  }
}

medium

A. The save method does not exist in repositories

B. The repository is not injected, so it will cause a NullPointerException

C. The service class must be abstract

D. The Product parameter should be annotated with @Entity

Solution

1. Step 1: Check repository injection

   The repository field is declared but not injected or initialized.

2. Step 2: Understand consequence of missing injection

   Calling save on a null repository causes NullPointerException at runtime.

3. Final Answer:

   The repository is not injected, so it will cause a NullPointerException -> Option B

4. Quick Check:

   Missing injection causes null pointer error [OK]

Hint: Always inject repository before use [OK]

Common Mistakes:

• Forgetting @Autowired or constructor injection
• Assuming repository auto-initializes
• Confusing entity annotation with parameter

5. You want to create a service method that returns all active users from the database. The repository has a method List<User> findByActiveTrue(). How should the service method call the repository and return the list?

hard

A. public List<User> getActiveUsers() { return userRepository.findByActiveTrue(); }

B. public List<User> getActiveUsers() { return userRepository.findAll(); }

C. public List<User> getActiveUsers() { return userRepository.findByActiveFalse(); }

D. public List<User> getActiveUsers() { return null; }

Solution

1. Step 1: Identify repository method for active users

   The repository method findByActiveTrue() returns users with active = true.

2. Step 2: Use repository method in service

   The service should call this method and return its result directly.

3. Final Answer:

   public List<User> getActiveUsers() { return userRepository.findByActiveTrue(); } -> Option A

4. Quick Check:

   Call matching repository method for active users [OK]

Hint: Call repository method matching your filter [OK]

Common Mistakes:

• Calling findAll() returns all users, not filtered
• Using findByActiveFalse() returns inactive users
• Returning null instead of data