Why Constructor injection (preferred) in Spring Boot? - Purpose & Use Cases

The Big Idea

Discover how a simple constructor can save you hours of debugging and messy code!

The Scenario

Imagine building a Spring Boot app where you manually create and connect all your service objects inside your code.

You have to write extra code to create each dependency and pass it around everywhere.

The Problem

Manually creating and wiring dependencies is slow and error-prone.

You might forget to create a needed object or pass the wrong one, causing bugs that are hard to find.

It also makes your code messy and hard to test.

The Solution

Constructor injection lets Spring automatically provide the needed objects when creating your classes.

This means your classes clearly state what they need, and Spring handles the rest.

It makes your code cleaner, safer, and easier to test.

Before vs After

✗ Before

public class UserService {
  private EmailService emailService;
  public UserService() {
    this.emailService = new EmailService();
  }
}

✓ After

public class UserService {
  private final EmailService emailService;
  public UserService(EmailService emailService) {
    this.emailService = emailService;
  }
}

What It Enables

It enables clear, reliable, and testable code where dependencies are managed automatically.

Real Life Example

When building a web app, constructor injection ensures your UserService always gets the right EmailService without extra setup code.

Key Takeaways

Manual dependency setup is error-prone and messy.

Constructor injection lets Spring provide dependencies automatically.

This leads to cleaner, safer, and easier-to-test code.