Java Bean Bag

🏗 Structure 1️⃣ Setting the Scene — The Confusion Moment 🤔 "I thought JSON was just a HashMap in a superhero costume!!" Nope! It’s like saying Spring Boot is just Spring MVC with coffee ☕ — there’s way more going on. 2️⃣ 💡 What is a HashMap? Java-only data structure Stores key-value pairs in memory (heap) Keys can be anything — Integer, String, custom objects (if hashCode() & equals() are implemented properly) Not meant for network transfer 📦 Example: Map<Integer, String> studentMap = new HashMap<>(); studentMap.put(101, "Anand"); studentMap.put(102, "Priya"); This stays inside your JVM. If you try to send it over HTTP as-is… good luck explaining it to a Python service. 🐍💥 3️⃣ 📝 What is JSON? Language-independent data format (Java, Python, JS, Go, you name it) Stores only String...

☕ Spring Bean Scopes – Explained Like You’re Shopping Online 🛒 In one of my interviews, I was asked a simple question: "What are the scopes in Spring and when will you use them?" I thought I knew it... until the interviewer confused me so much that I started mixing prototype with singleton and session with application 🤯. So here’s my real-time, e-commerce-style explanation of Spring bean scopes — with code, diagrams, and some fun analogies! 1️⃣ Singleton Scope – 📦 The Universal Product Definition: Spring creates only one instance of the bean for the entire application context. Every @Autowired injection gets the same object . 🛒 E-Commerce Example: Think of Amazon's Shipping Service . Every order uses the same logic, the same configuration — no need to create a new object for each request. @Component @Scope("singleton") // Default one , So you don't want to mention explicitly public class ShippingService { private String shipp...

💥 “Filter vs Interceptor in Spring — Who’s the Real Gatekeeper?” 🔍 The Hidden Guards of Your REST APIs (with Real Examples, Jokes & Weird Discoveries!) 🎯 1) What Is Filter / Interceptor / OncePerRequestFilter? 🧹 Filter A Filter is a component from the Servlet API that sits at the very beginning of a request's journey. It is invoked before the Spring context even gets involved. It's great for tasks like CORS configuration, encoding setup, basic logging, and blocking or modifying raw requests/responses. 🎤 Think of Filter as the club bouncer who checks everyone at the entrance—before they even see the dance floor! 🕵️ Interceptor A HandlerInterceptor is a Spring MVC feature that works after the request has passed through the DispatcherServlet but before the controller method is executed. It can inspect the handler (controller) method, add attributes, or block the request if needed. 🤓 It’s like the guy inside the club checking if you’re VIP before letting you in ...

💡 Lesson Learned — Not a Prod Bug, But a Real Pain No, this wasn’t a production outage. Nobody screamed at me. But I sat for 3 hours wondering: “Why the heck is my @Transactional not rolling back!?” 😵‍💫 “Why is Redis cache not working?” 🤯 Turned out, the issue was one silent villain: 🧱 Self-invocation 🤷 What Is @Transactional ? If you're new: @Transactional = Tells Spring to start a DB transaction when a method is called. It’ll commit if everything’s okay. It’ll rollback if something fails. 🧠 Think of it like wrapping your code in: try { beginTransaction(); // your logic commit(); } catch(Exception e) { rollback(); } 🕵️ Real-Life Analogy — The Gateway Community 🏘️ Let me tell you about my society — it has a strict watchman at the gate. Here’s how it works: 🛂 Watchman = Spring Proxy 🏠 Your apartment = Your service class 🚪 Your room = A method inside that class 🏃 Scenario 1: Outsider Visits Your friend from outside...

🔍  A surprising Spring Boot moment I didn't expect — and the rabbit hole it took me down... 🎬 It All Started With a Simple Idea... You know how it goes… You define a config value like this in application.properties : payment.currency=INR And then you boldly write this innocent-looking code: @Component public class PaymentUtil { @Value("${payment.currency}") private static String currency; // ✅ Logical! Right? public static void printCurrency() { System.out.println("Currency: " + currency); } } You run the app. And BAM 💥 Currency: null 😵 "Eh? I clearly defined the property. Is it not reading the file? Do I need a restart? Do I need to yell at my laptop?" 🤯 The Shocking Discovery Spring doesn’t inject values into static fields. Yes, my friend. Even if you beg it with @Value . And trust me — it’s not a bug. It’s a feature. 🙃 🧠 What Is This Dependency Injection (DI) Sorcery ...

 🧠 Ever looked at these two annotations and thought: “Aren’t they doing the same thing ?” Welcome to the club. I had the same confusion until... I went deep down the Spring rabbit hole 🕳️🐇 Let’s clear this once and for all — with real differences , examples , gotchas , and even a few bad jokes along the way 😎 🌟 The Basic Definitions Annotation Meaning @Component A general-purpose stereotype indicating a class is a Spring-managed bean @Configuration A specialized class used to declare beans via @Bean methods 💡 Both register beans with Spring — but what happens behind the scenes is where it gets spicy 🌶️ 🤔 But Aren’t They Both Just “Beans”? Short answer: Yes . Long answer: It’s complicated — like your last relationship 💔. ⚙️ INTERNAL MAGIC: The Real Difference 1. @Con...

  🌪️ The Chaos Begins It was a normal day in production... until suddenly, one server started heating up 🔥. And I don’t mean metaphorically — its CPU usage shot up to 100% and stayed there, like it had chugged 10 cups of espresso ☕💥. No OutOfMemoryError. No Exceptions. No logs screaming for help. Just... silence and a fan spinning like a helicopter 🌀. 🧩 The Initial Clues We SSH'd into the server and ran: top -H -p <java_process_id> We noticed one thread hogging the CPU — continuously. Then we used VisualVM to peek inside. Stack trace of that CPU-hogging thread looked like this: at com.example.MyProcessor.process(MyProcessor.java:42) at com.example.MyProcessor.run(MyProcessor.java:30) ... Hmm… That class wasn’t doing anything fancy. Just a retry mechanism inside a loop. 🔍 The Suspect Code Here’s what the code looked like: while ( true ) { try { doSomeCriticalOperation(); break ; // Exit on success } catch (Exception e) { ...

 Hey devs 👋, A few years back (around 3–4 years ago), I got a chance to work on a project involving Spring Cron Scheduler — using both XML configuration and Java annotations . The requirement was pretty standard: ✅ Trigger a job every day at a particular time ✅ Fetch data from a table maintained by another team ✅ Process that data further Everything worked well at first — in lower environments and even after initial production deployment . But then... something strange started happening 😬 🚨 The Weird Behavior After 4-5 days in production, the scheduled method started behaving oddly: ❌ It triggered twice at the same time ❌ Then later, three times , then four ... 😵 Restarting the application fixed it — but only temporarily . After a few more days, it would go back to calling multiple times again. It was as if my @Scheduled method had cloned itself and started a party! 🥴 ⏳ Take 10 Seconds... Can You Guess the Root Cause? You probably thought of: Duplica...

👋 Before diving deep into testing, I always assumed: "JUnit is just something you use with @Test… it just works!"   But once I actually started exploring test frameworks in real-world projects, I realized there's so much more behind the scenes. So here’s a blog to clarify the confusion , make it visually digestible , and hopefully save you some debugging hours . Let’s roll! 🧠✨ 🔍 Step 1: What dependencies should I include for JUnit? You may have seen these terms in your build.gradle : testImplementation 'org.junit.jupiter:junit-jupiter:5.10.0' implementation 'com.example:some-library:1.2.3' But wait... what’s the difference? 🤔 ✅ implementation This means: Include the library for both compile time AND runtime . It will be packaged inside the final JAR/WAR. Use it for things your production code needs. 🧪 testImplementation This means: Use it only during test execution . It will NOT be added to the production JAR/WAR. Perfect for JU...