Swift Concurrency: Structured Tasks Instead of Callback Pyramids
Swift's async/await, Task, and actors gave Apple's platforms a structured concurrency model so cancellation and isolation could be compiler-visible instead of GCD folklore.
Tag
15 articles · 52 min of reading
Swift's async/await, Task, and actors gave Apple's platforms a structured concurrency model so cancellation and isolation could be compiler-visible instead of GCD folklore.
How Snowflake scales a virtual warehouse out with extra clusters so queued queries get hardware instead of waiting behind a dashboard storm.
What structured concurrency adds on top of virtual threads: scopes, cancellation that actually propagates, and how it compares to CompletableFuture spaghetti.
OpenJDK's jcstress harness: litmus tests, outcome histograms, and how to catch publication bugs that unit tests will never see.
JSR-133: what synchronization actually publishes, why double-checked locking needed a rewrite, and how to reason without folklore.
Thompson, Farley, Barker, and co. on the Disruptor: ring buffers, sequence barriers, and avoiding locks when microseconds are the product.
When worker threads should share a buffer, how Atomics.wait and compareExchange actually work, and the security history that still gates SAB.
How Erlang's lightweight process model and deep FreeBSD tuning let WhatsApp run hundreds of millions of users' traffic with a remarkably small team.
Why the default executors behind @Scheduled and @Async are wrong for production, and how to configure thread pools that actually match your workload.
Why deadlocks happen even in well-designed schemas, how to read a deadlock log, and the lock-ordering habits that prevent them.
Beyond synchronized and Thread, java.util.concurrent has a purpose-built tool for nearly every coordination problem. Here's when to reach for each.
CompletableFuture's API surface is huge and easy to misuse. These are the composition patterns that hold up in real asynchronous pipelines.
Virtual threads remove the cost of blocking, not the need for careful concurrency design. Here's exactly what improves and what stays your problem.
How Postgres lets readers and writers proceed without blocking each other, what a snapshot actually is, and where MVCC's costs show up later.
A tour of READ UNCOMMITTED through SERIALIZABLE, the dirty reads and phantom rows each level permits, and how to pick one without guessing.