Java Synchronized Keyword for Thread Safety

Day 8/100 — Mastering Strings in Java 🔤 Today I explored one of the most important topics in Core Java: Strings. Every Java developer should clearly understand these three concepts: 1️⃣ Immutability In Java, a String object cannot be changed after it is created. Any modification actually creates a new object in memory. 2️⃣ String Pool Java optimizes memory using the String Pool. When we create strings using literals, Java stores them in a special memory area and reuses them. 3️⃣ equals() vs == • equals() → compares the actual content of two strings • == → compares memory references (whether both variables point to the same object) 💻 Challenge I practiced today: Reverse a String using charAt() method. Example logic: String str = "Java"; String reversed = ""; for (int i = str.length() - 1; i >= 0; i--) { reversed += str.charAt(i); } System.out.println(reversed); Small concepts like these build strong Java fundamentals. Consistency is key in this 100 Days of Code journey 🚀 #Java #CoreJava #JavaLearning #Strings #Programming #DeveloperJourney #100DaysOfCode

💡 Choosing GC in Java: What You Control vs What You Don’t While diving into JVM internals, I found a key concept about Garbage Collection (GC) that’s often misunderstood 👇 👉 In Java, we can choose which Garbage Collector to use But… 👉 We cannot control when it actually runs 🔍 Which GC is used by default? ✔ Before Java 8 → Parallel GC (Throughput Collector) ✔ Java 9 and above → G1 GC (Garbage First) ✅ ⚙️ How to choose a GC? (JVM Commands) 👉 Run your program like this: java -XX:+UseSerialGC MyProgram java -XX:+UseParallelGC MyProgram java -XX:+UseG1GC MyProgram java -XX:+UseZGC MyProgram 🧠 Basic Functionality of Popular GCs 🔹 Parallel GC (Throughput GC) ✔ Uses multiple threads for garbage collection ✔ Focuses on maximum throughput (performance) ❌ Causes Stop-The-World (STW) pauses 👉 Best for applications where speed > pause time 🔹 G1 GC (Garbage First) ✔ Divides heap into regions instead of generations ✔ Collects regions with maximum garbage first ✔ Provides low and predictable pause times 👉 Best for large-scale and modern applications 💡 Even if you call: System.gc(); ❌ It does NOT guarantee GC ✔ It’s just a request — JVM may ignore it 🔑 Key Takeaways: ✔ We control the type of GC (policy) ✔ JVM controls execution (timing & behavior) ✔ GC runs based on memory usage & internal algorithms ✔ Forcing GC can hurt performance 🚀 Interview Insight: “System.gc() is a suggestion, not a command.” Understanding this changed how I see JVM — it's highly optimized and smarter than manual control. 👉 We choose the GC, but JVM decides its execution. #Java #JVM #GarbageCollection #BackendDevelopment #JavaDeveloper #Programming #InterviewPreparation

Understanding == vs .equals() in Java 🔍 As I start sharing on LinkedIn, I thought I'd kick things off with a fundamental Java concept that often trips up developers: the difference between == and .equals() **The == Operator:** → Compares memory addresses (reference equality) → Checks if two references point to the exact same object → Works for primitives by comparing actual values **The .equals() Method:** → Compares the actual content of objects → Can be overridden to define custom equality logic → Default implementation in Object class uses == (unless overridden) Here's a practical example: String str1 = new String("Java"); String str2 = new String("Java"); str1 == str2 → false (different objects in memory) str1.equals(str2) → true (same content) **Key Takeaway:** Use == for primitives and reference comparison. Use .equals() when you need to compare the actual content of objects. This fundamental concept becomes crucial when working with Collections, String operations, and custom objects in enterprise applications. What other Java fundamentals would you like me to cover? Drop your suggestions in the comments. #Java #Programming #SoftwareDevelopment #BackendDevelopment #CodingTips #JavaDeveloper

🚀 Day 3/100 – Java Practice Challenge Continuing my #100DaysOfCode journey with another important core Java concept. 🔹 Topics Covered: Generics in Java Understanding type safety, reusability, and avoiding runtime errors. 💻 Practice Code: 🔸 Generic Class Example class Box { private T value; public void set(T value) { this.value = value; } public T get() { return value; } } 🔸 Usage Box intBox = new Box<>(); intBox.set(10); Box strBox = new Box<>(); strBox.set("Hello"); System.out.println(intBox.get()); // 10 System.out.println(strBox.get()); // Hello 📌 Key Learning: ✔ Generics provide compile-time type safety ✔ Avoid ClassCastException ✔ Help write reusable and clean code ⚠️ Important: • Use <?> for unknown types (wildcards) • Use for bounded types • Generics work only with objects, not primitives 🔥 Interview Insight: Generics use type erasure — type information is removed at runtime Widely used in collections like List, Map<K, V> 👉 Without Generics: List list = new ArrayList(); list.add("Java"); list.add(10); // No compile-time error ❌ #100DaysOfCode #Java #JavaDeveloper #Generics #CodingJourney #LearningInPublic #Programming

🔥 String vs StringBuilder in Java In Java, String is immutable and StringBuilder is mutable — and that makes a big difference in performance. 🔹 String • Immutable (cannot be changed after creation) • Every modification creates a new object in memory • Slower when used inside loops • Thread-safe ⚠️ Repeated concatenation (like in loops) leads to unnecessary object creation and memory usage. 🔹 StringBuilder • Mutable (modifies the same object) • No new object created for each change • Faster and memory efficient • Not thread-safe 🚀 Best choice for frequent string modifications, especially inside loops. 🎯 When to Use? ✅ Use String → When value doesn’t change ✅ Use StringBuilder → When performing multiple concatenations 💡 In backend applications, choosing StringBuilder for heavy string operations improves performance significantly. #Java #BackendDevelopment #JavaProgramming #Performance

Revision | Day 6 – Multithreading Today I explored the basics of Multithreading in Java and why it is important for building high-performance applications. What is Multithreading? Multithreading allows a program to execute multiple threads (smaller units of a process) simultaneously. It helps improve application performance and better CPU utilization. Thread vs Runnable There are two main ways to create threads in Java: 1. Extending Thread class class MyThread extends Thread { public void run() { System.out.println("Thread is running"); } } 2. Implementing Runnable interface (recommended) class MyRunnable implements Runnable { public void run() { System.out.println("Thread is running"); } } Runnable is preferred because Java supports single inheritance but multiple interfaces. Synchronization When multiple threads access shared resources, it may cause inconsistent results. Synchronization ensures that only one thread accesses the critical section at a time. Example: synchronized void increment() { count++; } Deadlock Deadlock occurs when two or more threads wait for each other to release resources, causing the program to freeze. Example scenario: Thread 1 → lock1 → waiting for lock2   Thread 2 → lock2 → waiting for lock1 Both threads get stuck forever. Key takeaway: Understanding multithreading is essential for building scalable backend systems and handling concurrent requests efficiently. #Java #Multithreading #BackendDevelopment #JavaDeveloper #LearningInPublic

📘 Abstract Class vs Interface in Java — Key Differences Today I explored one of the most important OOP concepts in Java: the difference between Abstract Classes and Interfaces. Both are used to achieve abstraction, but they serve different design purposes in Java applications. 🔹 Abstract Class • Supports partial abstraction • Can contain both abstract and concrete methods • Allows instance variables and constructors • Supports single inheritance using extends 🔹 Interface • Used for full abstraction (mostly) • Methods are public and abstract by default • Variables are public static final • Supports multiple inheritance using implements 💡 Key takeaway: Abstract classes are used when classes share common behavior, while interfaces define a contract that multiple unrelated classes can implement. Understanding when to use each helps in writing clean, scalable, and maintainable Java code. A special thanks to my mentor kshitij kenganavar sir for clearly explaining the concepts of Abstract Classes and Interfaces in Java. #Java #OOP #JavaProgramming #AbstractClass #Interface #SoftwareDevelopm

🚀 Starting My Java Learning Journey – Day 12 🔹 Topic: StringBuilder vs StringBuffer in Java In Java, StringBuilder and StringBuffer are used to create mutable (modifiable) strings, unlike String which is immutable. StringBuilder ✔ Not thread-safe ✔ Faster performance ✔ Used in single-threaded applications StringBuffer ✔ Thread-safe (synchronized) ✔ Slower than StringBuilder ✔ Used in multi-threaded applications 🔷 Program: public class Main { public static void main(String[] args) { StringBuilder sb = new StringBuilder("Hello"); sb.append(" World"); System.out.println("StringBuilder: " + sb); StringBuffer sbf = new StringBuffer("Hello"); sbf.append(" Java"); System.out.println("StringBuffer: " + sbf); } } Output: StringBuilder: Hello World StringBuffer: Hello Java 💡 Key Points: ✔ String → Immutable ✔ StringBuilder → Mutable & Fast ✔ StringBuffer → Mutable & Thread-safe #Java #JavaLearning #Programming #BackendDevelopment #CodingJourney #StringBuilder #StringBuffer

🚀 Java Series – Day 17 📌 File Handling in Java (I/O) 🔹 What is it? File handling in Java allows us to read from and write to files using input and output streams. 🔹 Why do we use it? It helps in storing and retrieving data from external sources like text files, logs, or configuration files. For example: In a real-world application, we use file handling to store user data, logs, or system configurations. 🔹 Example: import java.io.*; public class Main { public static void main(String[] args) { try { BufferedReader reader = new BufferedReader(new FileReader("test.txt")); String data = reader.readLine(); System.out.println("Read: " + data); reader.close(); } catch (IOException e) { System.out.println(e.getMessage()); } } } 💡 Key Takeaway: File handling is essential for data persistence and real-world application development. What do you think about this? 👇 #Java #JavaIO #FileHandling #JavaDeveloper #Programming #BackendDevelopment

📌Exception Handling in Java ⚠️ ✅Exception Handling is a mechanism to handle unexpected situations that occur while a program is running. When an exception occurs, it disrupts the normal flow of the program. Common examples: • Accessing an invalid index in an array→ ArrayIndexOutOfBoundsException • Dividing a number by zero→ ArithmeticException Java provides thousands of exception classes to handle different runtime problems. 📌 Types of Exceptions in Java 1️⃣ Built-in Exceptions These are predefined exceptions provided by Java. ✅Checked Exceptions -Checked by the compiler at compile time Must be handled using try-catch or declared using throws Examples: IOException SQLException ClassNotFoundException ✅Unchecked Exceptions -Not checked by the compiler at compile time Occur mainly due to programming errors Examples: ArithmeticException NullPointerException ClassCastException 2️⃣ User-Defined (Custom) Exceptions Java also allows developers to create their own exceptions. This is useful when we want to represent specific business logic errors. Basic rules to create a custom exception: 1️⃣ Extend the Exception class 2️⃣ Create a constructor with a message 3️⃣ Throw the exception using throw 4️⃣ Handle it using try-catch 📌 Finally Block ✅The finally block always executes after the try-catch block, whether an exception occurs or not. It is commonly used for cleanup tasks, such as: Closing database connections Closing files Releasing resources 📌 Try-With-Resources ✅Sometimes developers forget to close resources manually. To solve this problem, Java introduced Try-With-Resources. It automatically closes resources once the block finishes execution. This makes resource management safer and cleaner. 📌 Important Keywords ✅throw : Used to explicitly create and throw an exception object. ✅throws: Used in the method signature to indicate that a method may throw an exception. Grateful to my mentor Suresh Bishnoi Sir for explaining Java concepts with such clarity and practical depth . If this post added value, feel free to connect and share it with someone learning Java. #Java #ExceptionHandling #CoreJava #JavaDeveloper #BackendDevelopment #SoftwareEngineering #InterviewPreparation #JavaProgramming #CleanCode