Spring Boot: @Primary vs @Qualifier Annotation

🚀 Spring Boot Tip: @Qualifier vs @Primary (Fix Bean Ambiguity) Facing this error? 👇 "NoUniqueBeanDefinitionException" 👉 It means Spring found multiple beans of the same type and doesn’t know which one to inject. --- ✅ @Qualifier — Be Explicit Use "@Qualifier" when you want to specifically choose a bean. @Autowired @Qualifier("upiPaymentService") private PaymentService paymentService; ✔ You tell Spring exactly which implementation to inject ✔ Best when you have multiple beans and need control --- ✅ @Primary — Set a Default Use "@Primary" to mark one bean as the default choice. @Component @Primary class CreditCardPaymentService implements PaymentService {} ✔ Spring will pick this automatically ✔ Works when no "@Qualifier" is specified --- 🧠 Key Difference 👉 "@Qualifier" = Explicit selection 👉 "@Primary" = Default fallback --- ✨ Pro Tip If both are present: ➡️ "@Qualifier" overrides "@Primary" --- #SpringBoot #Java #BackendDevelopment #CodingTips #SoftwareEngineering

Most developers use Spring… but don’t fully understand what it’s actually doing under the hood. Here’s the reality 👇 Earlier, we used to create objects manually using new. That means we controlled everything — object creation, dependency wiring, lifecycle. But that approach leads to: ❌ Tight coupling ❌ Hard-to-test code ❌ Difficult maintenance Spring flips this completely. Instead of us controlling objects, Spring takes control — this is Inversion of Control (IoC). Now the container: ✔ Creates objects ✔ Injects dependencies ✔ Manages lifecycle And this is where Dependency Injection (DI) comes in. From experience and best practices: Constructor Injection → most reliable (preferred) Setter Injection → useful but optional Field Injection → avoid in real projects Another thing many people ignore is the Bean Lifecycle. A Spring Bean is not just created and used — it goes through: ➡ Creation ➡ Dependency Injection ➡ Initialization (@PostConstruct) ➡ Proxy wrapping (like @Transactional) ➡ Destruction (@PreDestroy) Understanding this is what separates: 👉 Someone who “uses Spring” vs 👉 Someone who can debug, design, and scale Spring applications If you're working on real-world backend systems, this is not optional knowledge. This is the foundation. #Spring #SpringBoot #Java #Backend #Microservices #IoC #DependencyInjection

🚀 Day 25 & 26 — Backend Debugging, Optimization & Documentation Focused on improving the quality of my Spring Boot Job Portal backend beyond just “working code”. 🔐 Auth & Security Fixes: • Fixed JWT handling — invalid/expired tokens now return proper 401 instead of 500 • Removed redundant DB query during login using authenticate.getPrincipal() • Standardized constructor-based dependency injection ⚡ Performance Improvements: • Eliminated double DB lookups using optimized repository methods (JOIN-based queries) • Fixed N+1 query issue using JOIN FETCH • Added @Transactional(readOnly = true) for better Hibernate performance 🛡️ Logic & Stability Fixes: • Prevented unintended reset of employer verification • Handled null cases using Optional (avoided runtime crashes) ⚠️ Error Handling Overhaul: Implemented GlobalExceptionHandler with proper mappings: • 404 → Resource not found • 401 → Unauthorized • 403 → Access denied • 409 → Conflict • 500 → Only for unexpected errors 📄 Day 26 — Documentation Upgrade: • Improved README with API endpoints • Added setup & deployment instructions • Documented architecture & authentication flow 💡 Key Learning: A good backend is not just about building features — it’s about handling edge cases, optimizing performance, and writing clean, maintainable code. #SpringBoot #Java #BackendDevelopment #100DaysOfCode #LearningInPublic

❓ What is the difference between @Controller and @RestController in Spring Boot? I’ve been working on backend development using Spring Boot and came across both annotations. Would love to understand the real difference and when to use each in real-world projects. Looking forward to your insights! #Java #SpringBoot #BackendDeveloper

Most people use Spring Boot. But very few understand what actually happens when the application starts While going deeper into it, a few things started making more sense How the application context is created What SpringBootApplication really triggers How the bean lifecycle actually works Why proxies are used for things like Transactional And how self invocation can silently break things It is easy to write Spring code Understanding what happens inside is different Still learning and connecting the dots What part of Spring feels confusing to you #Java #SpringBoot #BackendDevelopment #SoftwareEngineering #JavaDeveloper #SystemDesign #Placements

Spring Boot 4.0.3 is here! 🚀 The latest update brings improvements in performance, dependency upgrades, and better support for modern Java features. From enhanced native compilation to improved observability, this release continues to push Spring Boot forward. 💡 If you’re working with Spring, it’s time to explore the 4.x ecosystem. #SpringBoot #Java #BackendDevelopment #Microservices #TechUpdates

🚨 Spring Boot Trap @Transactional looks simple. But it has rules. It works when: • Called from another bean • Public methods • Proxy is active It fails silently when: • Self-invocation • Wrong propagation • Async methods Result? Data inconsistency. Always test transaction boundaries. Don’t assume they work. #SpringBoot #Java #Transactions #Backend #BackendDevelopment #JavaDeveloper #SoftwareEngineering #TechTips #SoftwareEngineer

🚀 What Really Happens When You Hit an API in Spring Boot? (Most beginners skip this — don't be one of them!) When I first started using Spring Boot, I knew how to write an API — but I had no idea what happened the moment I hit that endpoint. Turns out, there's an entire journey happening behind the scenes. Here's the full flow, broken down simply 👇 🔹 Tomcat — The Gatekeeper Every request first lands on the embedded Tomcat server. It listens on port 8080 and receives the raw HTTP request before anything else. 🔹 DispatcherServlet — The Front Controller This is the real entry point of Spring MVC. One servlet handles every single request and decides where it needs to go — like a receptionist routing calls across an office. 🔹 Handler Mapping — The Directory DispatcherServlet doesn't guess. It asks Handler Mapping — which controller owns this URL and HTTP method? 🔹 Interceptor — The Security Check Before your code even runs, interceptors handle cross-cutting concerns — authentication, logging, rate limiting. 🔹 Controller → Service → Repository — The Layers You Already Know The request flows through your layered architecture exactly the way we discussed last time. Controller routes, Service processes, Repository fetches. 🔹 Jackson — The Translator On the way back, Jackson silently converts your Java object into JSON. No extra code needed. 🔹 Response — Back to the Client Clean JSON, delivered. 💡 The biggest shift for me? Realizing that even a simple GET /users/1 triggers an entire coordinated flow — and Spring Boot handles most of it invisibly, so you can focus on what matters. #SpringBoot #Java #BackendDevelopment #SoftwareEngineering #JavaDeveloper #SpringFramework #APIDesign #CodingJourney

🚀 Mastering Spring Boot – Step by Step (Day 2) Still using "new" in Spring? ❌ 👉 Then you’re missing the core idea of Spring 💡 What is a Spring Bean? A Bean is: 👉 Any object managed by the Spring IoC container Instead of: UserService service = new UserService(); Spring does: ✔ Create objects ✔ Manage lifecycle ✔ Connect components 💡 What is IoC (Inversion of Control)? 👉 You don’t control object creation anymore 👉 Spring does it for you This leads to: ✔ Cleaner code ✔ Loose coupling ✔ Better scalability 💡 Simple way to think: You: "I will create objects" ❌ Spring: "I will handle everything" ✅ 👉 This is the foundation of Spring Next → Dependency Injection (real magic begins) 🔥 #Spring #SpringBoot #Java #Backend #LearningInPublic