Java: What is the difference between Virtual Threads and Platform Threads?

Virtual threads — managed by JVM. Platform threads — managed by OS.

Platform threads:

• One-to-one with OS threads.
• Limited by OS (thousands).
• Blocking blocks OS thread.
• Thread stack ~1MB.
• Preemptive scheduling.
• Can be daemon or non-daemon.

1Thread pt = new Thread(() -> { });
2// Platform thread by default
3
4Thread ptDaemon = new Thread(() -> { });
5ptDaemon.setDaemon(true);
6// Daemon platform thread

Virtual threads:

• Managed by JVM scheduler.
• Millions possible.
• Blocking doesn't block OS thread.
• Stack starts small, grows as needed.
• Always daemon threads.
• Cannot be stopped or interrupted while in synchronized blocks.

1Thread vt = Thread.ofVirtual().start(() -> { });
2// Virtual thread
3
4// Naming virtual threads
5Thread vtNamed = Thread.ofVirtual()
6    .name("worker-", 0)
7    .start(() -> { });

Key differences:

• Platform: limited, heavyweight.
• Virtual: scalable, lightweight.
• Virtual uses carrier threads (platform threads) for execution.
• Virtual threads are always daemon threads (won't prevent JVM shutdown).
• Platform threads can be joined with Thread.join(), virtual threads use Thread.join() too but may behave differently with structured concurrency.

System design context:

• Virtual threads are ideal for microservices handling thousands of concurrent HTTP requests.
• They reduce the need for complex reactive programming patterns.
• Can simplify blocking I/O code while maintaining high concurrency.

Common pitfalls:

• Pinning: Using synchronized blocks can pin virtual threads to carrier threads.
• ThreadLocal: Virtual threads inherit ThreadLocal values from parent, which can cause memory leaks.
• Monitoring: Virtual threads don't show up in traditional thread dumps the same way.

Production configuration:

1// Configure carrier thread pool size
2System.setProperty("jdk.virtualThreadScheduler.parallelism", "1");
3System.setProperty("jdk.virtualThreadScheduler.maxPoolSize", "1");

Monitoring/observability:

• Use jcmd Thread.dump_to_file -format=json for virtual thread dumps.
• Monitor carrier thread pool metrics.
• Track virtual thread creation and termination rates.