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.

Practice

1. What is the main role of a Spring Boot repository in database orchestration?

easy

A. To provide methods for saving, reading, updating, and deleting data

B. To define the database schema manually

C. To handle user interface rendering

D. To manage application security settings

Solution

1. Step 1: Understand repository purpose

   Spring Boot repositories act as a bridge between the app and the database, offering easy data operations.

2. Step 2: Identify repository capabilities

   They provide built-in methods like save(), findById(), delete(), which handle data safely without manual SQL.

3. Final Answer:

   To provide methods for saving, reading, updating, and deleting data -> Option A

4. Quick Check:

   Repository = Data operations [OK]

Hint: Repositories manage data actions like save and find [OK]

Common Mistakes:

• Confusing repositories with UI components
• Thinking repositories define database schema
• Assuming repositories handle security

2. Which of the following is the correct way to declare a Spring Data JPA repository interface for an entity User with primary key type Long?

easy

A. public interface UserRepository extends Repository<User> {}

B. public interface UserRepository extends JpaRepository {}

C. public class UserRepository implements JpaRepository {}

D. public interface UserRepository extends CrudRepository {}

Solution

1. Step 1: Recall correct interface extension

   Spring Data JPA repositories extend JpaRepository to get full CRUD support.

2. Step 2: Check syntax correctness

   public interface UserRepository extends JpaRepository {} correctly extends JpaRepository with User entity and Long ID type; others misuse implements or wrong generics order.

3. Final Answer:

   public interface UserRepository extends JpaRepository {} -> Option B

4. Quick Check:

   JpaRepository syntax [OK]

Hint: Use extends JpaRepository for repositories [OK]

Common Mistakes:

• Using implements instead of extends
• Swapping generic type order
• Extending incomplete Repository interface

3. Given the following Spring Boot repository method call:

Optional<User> user = userRepository.findById(5L);

What will user.isPresent() return if no user with ID 5 exists in the database?

medium

A. true

B. Throws an exception

C. null

D. false

Solution

1. Step 1: Understand findById return type

   findById returns an Optional which is empty if no matching record is found.

2. Step 2: Check isPresent behavior

   isPresent() returns false when Optional is empty, meaning no user found.

3. Final Answer:

   false -> Option D

4. Quick Check:

   Optional empty means isPresent() = false [OK]

Hint: Optional.isPresent() false means no data found [OK]

Common Mistakes:

• Assuming isPresent() returns true always
• Expecting null instead of Optional
• Thinking it throws exception if not found

4. Consider this Spring Boot repository interface:

public interface ProductRepository extends JpaRepository {
    List<Product> findByName(String name);
}

Which of the following issues will cause a runtime error when calling findByName(null)?

medium

A. No error; it returns an empty list

B. Method signature is invalid and won't compile

C. Calling findByName with null returns all products

D. Passing null causes a NullPointerException in query generation

Solution

1. Step 1: Analyze null parameter in derived queries

   Spring Data JPA derived query methods accept null parameters and generate SQL like WHERE name = null, which matches no rows (since NULL = NULL is false).

2. Step 2: Confirm behavior

   No exception is thrown at runtime or compile time; it safely returns an empty list.

3. Final Answer:

   No error; it returns an empty list -> Option A

4. Quick Check:

   findByName(null) = empty list [OK]

Hint: Null args in derived queries return empty lists safely [OK]

Common Mistakes:

• Thinking null causes NullPointerException
• Believing signature won't compile
• Assuming null returns all products

5. You want to update a user's email in the database using Spring Boot. Which sequence correctly orchestrates this update using repository methods?

1. Retrieve user by ID
2. Change user's email
3. Save updated user back to database

Which code snippet correctly implements this?

hard

A. userRepository.save(new User(id, newEmail));

B. userRepository.updateEmailById(id, newEmail);

C. var user = userRepository.findById(id).orElseThrow(); user.setEmail(newEmail); userRepository.save(user);

D. userRepository.findById(id).getEmail(newEmail); userRepository.save();

Solution

1. Step 1: Retrieve user safely

   Use findById(id).orElseThrow() to get user or throw if missing.

2. Step 2: Modify user object

   Set new email on retrieved user object.

3. Step 3: Save updated user

   Call save(user) to persist changes back to database.

4. Final Answer:

   var user = userRepository.findById(id).orElseThrow(); user.setEmail(newEmail); userRepository.save(user); -> Option C

5. Quick Check:

   Retrieve, modify, save = update pattern [OK]

Hint: Retrieve entity, change fields, then save [OK]

Common Mistakes:

• Trying to save new object without ID
• Using non-existent updateEmailById method
• Calling getEmail() instead of setEmail()