> For the complete documentation index, see [llms.txt](https://www.pranaypourkar.co.in/the-programmers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pranaypourkar.co.in/the-programmers-guide/spring/core-concepts/spring-beans/lazy-and-eager-initialization/use-case-of-lazy-initialization.md).

# Use Case of Lazy Initialization

## **Loading Optional Features in a Web Application**

### **Scenario**

In a **Spring Boot e-commerce application**, there is an **email notification service** that sends order confirmation emails. However, this service is **optional**—it should only be initialized when email notifications are enabled.

### **Problem without Lazy Initialization**

If the email notification service is **eagerly initialized**, it loads on **every application startup**, even when the feature is disabled. This increases startup time and unnecessarily loads dependencies like SMTP configurations.

### **Solution with Lazy Initialization**

Mark the email service as **lazy**, ensuring it is only loaded **when actually needed** (i.e., when an order is placed and email notifications are enabled).

**Implementation**

```java
@Component
@Lazy
public class EmailNotificationService {
    
    public EmailNotificationService() {
        System.out.println("EmailNotificationService Initialized");
    }

    public void sendOrderConfirmation(String email, String orderId) {
        System.out.println("Sending order confirmation to: " + email);
    }
}
```

**Usage in Order Processing**

```java
@Service
public class OrderService {
    
    private final EmailNotificationService emailService;

    public OrderService(EmailNotificationService emailService) {
        this.emailService = emailService;
    }

    public void processOrder(String email, String orderId, boolean emailEnabled) {
        System.out.println("Processing Order: " + orderId);
        if (emailEnabled) {
            emailService.sendOrderConfirmation(email, orderId);
        }
    }
}
```

**Behavior**

* If `emailEnabled = false`, the `EmailNotificationService` **never initializes**, saving memory and startup time.
* If `emailEnabled = true`, the service **initializes on demand** and sends the email.

### **Benefits of Lazy Initialization in this Case**

* **Faster Application Startup** – The email service isn’t loaded unless required.
* **Efficient Resource Utilization** – Avoids loading email configurations & SMTP dependencies when not needed.
* **Better Scalability** – Reduces overhead in applications where certain features are optional.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.pranaypourkar.co.in/the-programmers-guide/spring/core-concepts/spring-beans/lazy-and-eager-initialization/use-case-of-lazy-initialization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.