Service calling repository in Spring Boot

Introduction

Services call repositories to get or save data. This keeps code organized and easy to manage.

When you want to separate business logic from data access.

When you need to fetch data from a database in a clean way.

When you want to update or delete data safely.

When you want to reuse data access code in many places.

When you want to write tests for business logic without touching the database.

Syntax

Spring Boot

public class ServiceName {
    private final RepositoryName repository;

    public ServiceName(RepositoryName repository) {
        this.repository = repository;
    }

    public ReturnType someMethod() {
        return repository.someRepositoryMethod();
    }
}

Service classes use constructor injection to get repository instances.

Repository methods handle database operations like find, save, delete.

Examples

This service calls the repository to find a user by ID.

Spring Boot

public class UserService {
    private final UserRepository userRepository;

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

    public User findUserById(Long id) {
        return userRepository.findById(id).orElse(null);
    }
}

This service gets all products by calling the repository's findAll method.

Spring Boot

public class ProductService {
    private final ProductRepository productRepository;

    public ProductService(ProductRepository productRepository) {
        this.productRepository = productRepository;
    }

    public List<Product> getAllProducts() {
        return productRepository.findAll();
    }
}

Sample Program

This example shows a BookService calling BookRepository to get a book by its ID. The repository handles database access, and the service uses it to get the book data.

Spring Boot

import org.springframework.stereotype.Service;
import java.util.Optional;

@Service
public class BookService {
    private final BookRepository bookRepository;

    public BookService(BookRepository bookRepository) {
        this.bookRepository = bookRepository;
    }

    public Book getBookById(Long id) {
        return bookRepository.findById(id).orElse(null);
    }
}

import org.springframework.data.jpa.repository.JpaRepository;
import org.springframework.stereotype.Repository;

@Repository
public interface BookRepository extends JpaRepository<Book, Long> {
}

import jakarta.persistence.Entity;
import jakarta.persistence.Id;

@Entity
public class Book {
    @Id
    private Long id;
    private String title;

    public Book() {}

    public Book(Long id, String title) {
        this.id = id;
        this.title = title;
    }

    public Long getId() {
        return id;
    }

    public void setId(Long id) {
        this.id = id;
    }

    public String getTitle() {
        return title;
    }

    public void setTitle(String title) {
        this.title = title;
    }
}

Important Notes

Always use constructor injection for better testability and immutability.

Services should not contain database code directly; repositories handle that.

Use Optional from repository methods to handle missing data safely.

Summary

Services call repositories to separate business logic from data access.

Use constructor injection to provide repositories to services.

Repositories handle database operations; services use them to get or save data.

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