Why Service calling repository in Spring Boot? - Purpose & Use Cases

The Big Idea

Discover how separating data access from business logic saves you hours of debugging and rewriting!

The Scenario

Imagine building a web app where you manually write code to fetch data from the database every time a user requests something. You mix database queries directly inside your business logic.

The Problem

This approach quickly becomes messy and hard to maintain. If you want to change how data is fetched, you must hunt through all your code. It's easy to introduce bugs and hard to test parts separately.

The Solution

Using a service calling a repository cleanly separates concerns. The repository handles data access, while the service focuses on business rules. This makes code easier to read, test, and update.

Before vs After

✗ Before

public class UserService {
  public User getUser(int id) {
    // direct DB query here
  }
}

✓ After

public class UserService {
  private UserRepository repo;
  public User getUser(int id) {
    return repo.findById(id);
  }
}

What It Enables

This pattern enables building clear, maintainable apps where data access and business logic evolve independently.

Real Life Example

Think of an online store: the service calculates discounts and rules, while the repository fetches product info from the database.

Key Takeaways

Manual data access mixed with business logic is hard to maintain.

Service calling repository separates concerns clearly.

This leads to cleaner, testable, and flexible code.

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