What 100DaysOfJava changed in how I investigate systems
This challenge started as a way to learn more Java. Over time, it became a way to follow confusion down to memory, coordination, performance, and failure modes.
This challenge started as a way to learn more Java. Over time, it became a way to follow confusion down to memory, coordination, performance, and failure modes.
A measured comparison of virtual threads and event loops, with a public benchmark suite and guidance for testing each model against a real workload.
Why one parallel file-processing run left CPU cores idle, how a fixed-batch Spliterator changed the result, and why the finding is tied to its runtime and workload.
I thought virtual threads were just green threads—turns out they’re continuations on the heap with sophisticated scheduling. Here’s what I got wrong and what actually happens under the hood.
Part 3: Advanced Patterns & Production Readiness - Deep dive into 3 advanced tools plus debugging, monitoring, and going to production