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.