0 of 4 done
How Java actually runs, and how to make it run correctly and fast under concurrent load. For a low-latency / systems-oriented target this is the highest-signal section in the domain — GC behavior, the memory model, and lock-free structures are exactly what such roles screen for. Part of the Java course.
- JVM Internals — class loading, bytecode, the JIT, the runtime memory areas (heap/stack/metaspace), garbage collection (generational, G1/ZGC, pause behavior), escape analysis, and tuning
- Concurrency — threads, thread-safety,
synchronized, the Java memory model (happens-before,volatile),java.util.concurrent(executors,CompletableFuture, atomics/CAS, locks), daemon threads, graceful shutdown - Virtual Threads — Project Loom: what changes when a thread costs almost nothing, structured concurrency, and where it does and doesn’t help
Practice
- Exercises — two unsolved, runnable exercises (a bounded blocking queue and a token-bucket rate limiter) with a red-to-green test harness. The notes give the vocabulary; these build the reps.
Related
- Collections — the thread-safe variants (
ConcurrentHashMap) live at the intersection of these two sections - Batch Processing & Performance — where GC and concurrency show up as real throughput numbers
- Java course index
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering