@PostConstruct and @PreDestroy in Spring Boot - Performance & Optimization

Performance: @PostConstruct and @PreDestroy

MEDIUM IMPACT

These annotations affect the initialization and cleanup phases of Spring beans, impacting application startup and shutdown time.

Running initialization logic after bean creation

Spring Boot

@PostConstruct
public void init() {
  // lightweight setup only
  this.cache = new HashMap<>();
  // defer heavy tasks to async methods
  asyncService.loadDataAsync();
}

Lightweight setup runs quickly; heavy tasks run asynchronously without blocking startup.

📈 Performance Gainstartup completes immediately, heavy tasks offloaded, improves app responsiveness

Running initialization logic after bean creation

Spring Boot

@PostConstruct
public void init() throws InterruptedException {
  // heavy logic like blocking IO or long loops
  Thread.sleep(5000);
}

Blocking or heavy operations in @PostConstruct delay application startup and block the main thread.

📉 Performance Costblocks startup for 5 seconds, delaying app readiness

Performance Comparison

Pattern	Blocking Operations	Startup Delay	Shutdown Delay	Verdict
Heavy blocking logic in @PostConstruct/@PreDestroy	Yes	High (seconds)	High (seconds)	[X] Bad
Lightweight logic with async offloading	No	Low (milliseconds)	Low (milliseconds)	[OK] Good

Rendering Pipeline

These annotations run methods during bean lifecycle events, affecting the app's startup and shutdown phases but not the browser rendering pipeline.

→Application Initialization

→Application Shutdown

⚠️ BottleneckBlocking or heavy operations inside these methods can delay startup or shutdown.

Optimization Tips

1Keep @PostConstruct methods lightweight to avoid blocking app startup.

2Avoid blocking calls in @PreDestroy to ensure fast application shutdown.

3Offload heavy or slow tasks to asynchronous processes outside lifecycle methods.

Performance Quiz - 3 Questions

What is the main performance risk of putting heavy blocking code inside @PostConstruct?

A It delays application startup and blocks the main thread.

B It causes layout shifts in the browser.

C It increases bundle size significantly.

D It improves application responsiveness.

DevTools: Spring Boot Actuator / Logs

How to check: Enable startup and shutdown logs; measure time taken by @PostConstruct and @PreDestroy methods in logs or use Actuator endpoints.

What to look for: Long delays or blocking calls during startup or shutdown phases indicate performance issues.

Practice

1. What is the main purpose of the @PostConstruct annotation in a Spring Boot application?

easy

A. To run a method immediately after the bean is created and dependencies are injected

B. To mark a method that should run before the bean is destroyed

C. To define a method that runs only when the application starts

D. To schedule a method to run repeatedly at fixed intervals

Solution

1. Step 1: Understand the role of @PostConstruct

   @PostConstruct is used to run initialization code after the Spring bean is fully created and dependencies are set.

2. Step 2: Compare with other lifecycle annotations

   @PreDestroy runs before bean removal, and scheduling annotations run repeatedly, so they don't match @PostConstruct's purpose.

3. Final Answer:

   To run a method immediately after the bean is created and dependencies are injected -> Option A

4. Quick Check:

   @PostConstruct = run after bean creation [OK]

Hint: Remember: PostConstruct runs right after bean setup [OK]

Common Mistakes:

• Confusing @PostConstruct with @PreDestroy
• Thinking @PostConstruct runs before bean creation
• Assuming it schedules repeated tasks

2. Which of the following is the correct way to use @PreDestroy in a Spring Boot bean?

easy

A. Place @PreDestroy on a static method to run after application shutdown

B. Annotate a method with @PreDestroy to run cleanup code before bean destruction

C. Use @PreDestroy on a constructor to initialize resources

D. Annotate the class with @PreDestroy to mark it for destruction

Solution

1. Step 1: Identify correct usage of @PreDestroy

   @PreDestroy is placed on a method to run cleanup code before the bean is destroyed.

2. Step 2: Eliminate incorrect options

   @PreDestroy cannot annotate a class or constructor, and static methods are not lifecycle callbacks.

3. Final Answer:

   Annotate a method with @PreDestroy to run cleanup code before bean destruction -> Option B

4. Quick Check:

   @PreDestroy = method cleanup before bean removal [OK]

Hint: Use @PreDestroy only on instance methods for cleanup [OK]

Common Mistakes:

• Annotating the class instead of a method
• Using @PreDestroy on constructors
• Marking static methods with @PreDestroy

3. Consider the following Spring Boot bean code snippet:

public class MyBean {

    @PostConstruct
    public void init() {
        System.out.println("Bean is initialized");
    }

    @PreDestroy
    public void cleanup() {
        System.out.println("Bean is about to be destroyed");
    }

}

What will be printed when the application context starts and then shuts down?

medium

A. Bean is about to be destroyedBean is initialized

B. Only Bean is initialized

C. Bean is initializedBean is about to be destroyed

D. Only Bean is about to be destroyed

Solution

1. Step 1: Understand @PostConstruct behavior on startup

   The init() method runs after bean creation, printing "Bean is initialized" when the app context starts.

2. Step 2: Understand @PreDestroy behavior on shutdown

   The cleanup() method runs before bean destruction, printing "Bean is about to be destroyed" when the app context shuts down.

3. Final Answer:

   Bean is initialized
   Bean is about to be destroyed -> Option C

4. Quick Check:

   Startup prints init, shutdown prints cleanup [OK]

Hint: PostConstruct runs on start, PreDestroy runs on shutdown [OK]

Common Mistakes:

• Mixing order of printed messages
• Expecting only one message to print
• Thinking @PreDestroy runs on startup

4. Given this Spring Boot bean code:

public class ResourceBean {

    @PostConstruct
    public void setup() {
        System.out.println("Setup resources");
    }

    @PreDestroy
    public void cleanup() {
        System.out.println("Cleanup resources");
    }

    public void start() {
        System.out.println("Start method called");
    }

}

When running the application, the developer notices that "Cleanup resources" is never printed on shutdown. What is the most likely cause?

medium

A. The @PostConstruct method prevents @PreDestroy from running

B. The @PreDestroy method must be static to run correctly

C. The cleanup() method must be called manually to run

D. The bean is not managed by Spring, so lifecycle annotations are ignored

Solution

1. Step 1: Check if bean is managed by Spring

   @PostConstruct and @PreDestroy only work if Spring manages the bean lifecycle (e.g., via @Component or @Bean).

2. Step 2: Understand why cleanup isn't called

   If the bean is created manually (new keyword), Spring won't call lifecycle methods, so cleanup() won't run automatically.

3. Final Answer:

   The bean is not managed by Spring, so lifecycle annotations are ignored -> Option D

4. Quick Check:

   Lifecycle annotations need Spring-managed beans [OK]

Hint: Lifecycle methods run only on Spring-managed beans [OK]

Common Mistakes:

• Thinking @PreDestroy must be static
• Assuming @PostConstruct blocks @PreDestroy
• Believing cleanup() runs without Spring management

5. You want to ensure a Spring Boot bean opens a database connection after creation and closes it before destruction. Which code snippet correctly uses @PostConstruct and @PreDestroy to achieve this?

hard

A. public class DbBean {

private Connection conn;

@PostConstruct
public void open() {
conn = DriverManager.getConnection("url");
System.out.println("Connection opened");
}

@PreDestroy
public void close() {
conn.close();
System.out.println("Connection closed");
}

}

B. public class DbBean {

private Connection conn;

public void open() {
conn = DriverManager.getConnection("url");
System.out.println("Connection opened");
}

public void close() {
conn.close();
System.out.println("Connection closed");
}

}

C. public class DbBean {

private Connection conn;

@PreDestroy
public void open() {
conn = DriverManager.getConnection("url");
System.out.println("Connection opened");
}

@PostConstruct
public void close() {
conn.close();
System.out.println("Connection closed");
}

}

D. public class DbBean {

private Connection conn;

@PostConstruct
public void open() {
System.out.println("Connection opened");
}

@PreDestroy
public void close() {
System.out.println("Connection closed");
}

}

Solution

1. Step 1: Identify correct lifecycle method usage

   @PostConstruct should open the connection after bean creation; @PreDestroy should close it before destruction.

2. Step 2: Check code correctness

   public class DbBean { private Connection conn; @PostConstruct public void open() { conn = DriverManager.getConnection("url"); System.out.println("Connection opened"); } @PreDestroy public void close() { conn.close(); System.out.println("Connection closed"); } } correctly uses @PostConstruct to open and @PreDestroy to close the connection with proper method calls.

3. Final Answer:

   public class DbBean { private Connection conn; @PostConstruct public void open() { conn = DriverManager.getConnection("url"); System.out.println("Connection opened"); } @PreDestroy public void close() { conn.close(); System.out.println("Connection closed"); } } -> Option A

4. Quick Check:

   Open after creation, close before destruction [OK]

Hint: Open in @PostConstruct, close in @PreDestroy for resource management [OK]

Common Mistakes:

• Swapping @PostConstruct and @PreDestroy methods
• Not calling connection methods inside lifecycle methods
• Missing lifecycle annotations on resource methods