How does the @Qualifier annotation work in Spring for managing dependencies?

Question

Accepted Answer

The @Qualifier annotation resolves ambiguity in Spring's dependency injection by letting a developer specify exactly which bean should be injected when multiple candidates of the same type exist in the context.

Key Points:
• Each candidate bean can be given a unique qualifier value, either through @Qualifier on the bean definition or derived from the bean name.
• At the injection point, adding @Qualifier("name") alongside @Autowired tells Spring precisely which bean to wire.
• Useful when different implementations of the same interface serve different purposes, like multiple notification channels.
• Custom qualifier annotations can be created for stronger typing than raw string-based qualifiers.
• Without @Qualifier in an ambiguous situation, Spring fails fast at context startup rather than guessing.

Example:
Two NotificationService implementations, EmailNotificationService and SmsNotificationService, both implement NotificationService; @Qualifier("smsNotificationService") ensures the SMS variant is injected into a specific class that must send text alerts.

Code Example:
```
@Autowired
@Qualifier("smsNotificationService")
private NotificationService notificationService;
```

Interview Tip:
A concise interview answer is:

"@Qualifier resolves the ambiguity that comes up when multiple beans implement the same interface. I pair it with @Autowired and specify the bean name so Spring injects the exact implementation I need, which is common when I have multiple strategy-style implementations like different notification channels."