🌱 Spring Bean Lifecycle

Spring beans don’t just appear… they go through a carefully choreographed life journey 🎭 From birth → preparation → service → retirement.

Let’s walk that lifecycle step by step.

---

🔹 1. Bean Instantiation (Birth)

Spring creates the bean object.

@Component
class MyService {
    public MyService() {
        System.out.println("Constructor called");
    }
}

👉 Bean is born using constructor or factory method.

---

🔹 2. Populate Properties (Dependency Injection)

Spring injects dependencies:

@Autowired
private AnotherService service;

👉 Like equipping the bean with tools 🧰

---

🔹 3. Aware Interfaces (Optional)

Bean gets context awareness:

• BeanNameAware
• ApplicationContextAware

@Override
public void setBeanName(String name) {
    System.out.println("Bean name: " + name);
}

👉 “Hey bean, you exist in this world, here’s your identity.”

---

🔹 4. BeanPostProcessor (Before Init)

Custom logic before initialization:

public Object postProcessBeforeInitialization(Object bean, String name)

👉 Used for:

• Logging
• Proxy creation
• Modifications

---

🔹 5. Initialization Phase

Two main ways:

✅ Using @PostConstruct

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

✅ Using InitializingBean

@Override
public void afterPropertiesSet() {
    System.out.println("After properties set");
}

👉 Bean is now fully ready 🚀

---

🔹 6. BeanPostProcessor (After Init)

public Object postProcessAfterInitialization(Object bean, String name)

👉 Often used for:

• AOP proxies
• Enhancements

---

🔹 7. Bean Ready for Use

Now the bean is:

• Fully initialized
• Managed by Spring container

👉 This is where your business logic runs

---

🔹 8. Destruction Phase (Shutdown)

When container shuts down:

✅ Using @PreDestroy

@PreDestroy
public void destroy() {
    System.out.println("Bean destroyed");
}

✅ Using DisposableBean

@Override
public void destroy() {
    System.out.println("Cleanup done");
}

👉 Cleanup resources (DB connections, threads, etc.)

---

🔄 Full Lifecycle Flow

Instantiate → Inject Dependencies → Aware Interfaces →
BeanPostProcessor (Before) → Init →
BeanPostProcessor (After) → Ready →
Destroy

---

🎯 Interview Answer (Concise)

“Spring bean lifecycle includes instantiation, dependency injection, awareness callbacks, pre-initialization processing, initialization via @PostConstruct or InitializingBean, post-initialization processing, and finally destruction using @PreDestroy or DisposableBean.”

---

🧠 Real Insight (Advanced)

• BeanPostProcessor is heavily used internally by Spring for:

  • AOP
  • Transactions
  • Security

👉 That’s how magic like @Transactional works ✨

---

⚠️ Common Mistakes

• Forgetting that:

  • @PostConstruct runs after dependency injection
  • @PreDestroy only works for singleton beans

---

🚀 Memory Trick

Think of it like a startup employee 👨‍💻

1. Hired (instantiate)
2. Given tools (DI)
3. Orientation (aware)
4. Training (init)
5. Works (ready)
6. Exit interview (destroy)