The Multi-Threading Fallacy: Why Management Keeps Misunderstanding System Design

madking.direct@gmail.com (Mad King) — Tue, 02 Jun 2026 00:00:00 +0000

Someone in a meeting somewhere is about to say: “let’s add multi-threading — it’ll speed things up.”

Every senior engineer just flinched. Because that sentence has killed more projects than bad requirements, understaffing, and legacy codebases combined.

Here’s the problem: threading is sold as a performance technique. In practice it’s a correctness technique used for a very narrow set of problems. And the number of times it actually delivers on its performance promise is small enough to count on one hand.

Building a High-Performance Orderbook in Java 24: The Data Structures That Actually Matter

madking.direct@gmail.com (Mad King) — Thu, 02 Apr 2026 00:00:00 +0000

I decided to build an orderbook from scratch.

Not as a homework exercise. Real market data. Real matching logic. The kind of thing that runs in production at exchanges and brokerages. And the most surprising thing wasn’t how hard it was — it was how much Java 24 simply got out of my way.

The orderbook is deceptively simple in concept: collect buy orders at various price levels, collect sell orders at various price levels, match them when they overlap. In practice, a naive implementation collapses under real-volume load. Here’s what changed when I leaned into the JVM properly.

Performance on Mad Blog

The Multi-Threading Fallacy: Why Management Keeps Misunderstanding System Design

Building a High-Performance Orderbook in Java 24: The Data Structures That Actually Matter