Database and app orchestration in Spring Boot - Performance & Optimization

Performance: Database and app orchestration

HIGH IMPACT

This concept affects how quickly the app communicates with the database and manages data flow, impacting page load and interaction speed.

Managing database queries and app data flow

Spring Boot

public List<User> getUsers() {
    return userRepository.findAllById(IntStream.range(0, 100).boxed().collect(Collectors.toList()));
}

This pattern batches queries into a single call, reducing database round trips and speeding up response.

📈 Performance GainSingle database call reduces blocking time and improves LCP and INP significantly.

Managing database queries and app data flow

Spring Boot

public List<User> getUsers() {
    List<User> users = new ArrayList<>();
    for (int i = 0; i < 100; i++) {
        users.add(userRepository.findById(i).orElse(null));
    }
    return users;
}

This pattern triggers 100 separate database queries, causing high latency and blocking the app thread.

📉 Performance CostTriggers 100 database calls, blocking rendering and increasing LCP by hundreds of milliseconds.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Multiple individual DB calls	N/A	N/A	Blocks rendering until data arrives	[X] Bad
Batch DB calls with async processing	N/A	N/A	Faster data delivery enables quicker paint	[OK] Good

Rendering Pipeline

Database and app orchestration affects the time before the app can send data to the browser, impacting the critical rendering path by delaying content availability.

→Data Fetching

→Server Processing

→Network Transfer

→Rendering

⚠️ BottleneckData Fetching and Server Processing due to inefficient queries or orchestration

Core Web Vital Affected

LCP, INP

This concept affects how quickly the app communicates with the database and manages data flow, impacting page load and interaction speed.

Optimization Tips

1Batch database queries to reduce network round trips.

2Use asynchronous processing to avoid blocking the app thread.

3Cache frequent data to minimize repeated database calls.

Performance Quiz - 3 Questions

What is a major performance issue when an app makes many individual database calls instead of batching them?

A Increased network latency and blocking of rendering

B Reduced server CPU usage

C Improved caching efficiency

D Faster initial page load

DevTools: Network

How to check: Open DevTools, go to Network tab, filter XHR requests, and observe the number and timing of database API calls.

What to look for: Look for many small requests causing delays versus fewer batched requests with faster response times.