Java StringBuilder vs StringBuffer: Mutability, Thread-Safety & Speed

Because Java String objects are strictly immutable, every modification (concatenation, replacement, substring) creates a brand-new object on the Heap. When performing hundreds or thousands of string modifications, you must use mutable character buffers: StringBuilder or StringBuffer.

Side-by-Side Architectural Comparison

Performance Benchmark: String vs. StringBuilder

Observe the dramatic real-world performance difference when appending 50,000 strings in a loop:

public class StringBenchmark {
    public static void main(String[] args) {
        int iterations = 50_000;

        // Test 1: String Concatenation (+)
        long start1 = System.currentTimeMillis();
        String str = "";
        for (int i = 0; i < iterations; i++) {
            str += i; // Disaster: Creates 50,000 intermediate Heap objects!
        }
        long duration1 = System.currentTimeMillis() - start1;
        System.out.println("String (+) time:         " + duration1 + " ms (~1,800 ms)");

        // Test 2: StringBuilder (.append())
        long start2 = System.currentTimeMillis();
        StringBuilder sb = new StringBuilder();
        for (int i = 0; i < iterations; i++) {
            sb.append(i); // In-place buffer modification!
        }
        long duration2 = System.currentTimeMillis() - start2;
        System.out.println("StringBuilder time:      " + duration2 + " ms (~3 ms)");
    }
}

Core StringBuilder Methods:

StringBuilder sb = new StringBuilder("Veewom");

sb.append(" Java");        // "Veewom Java"
sb.insert(6, " Master");   // "Veewom Master Java"
sb.replace(0, 6, "Learn"); // "Learn Master Java"
sb.delete(5, 12);          // "Learn Java"
sb.reverse();              // "avaJ nraeL"
String result = sb.toString(); // Converts back to immutable String