Ephemeral Signals - Turning Atoms into a Sensing Network

A tiny primitive that turns concurrent work into a coordinated, adaptive system. "The Ephemeral Signals Pattern" In Part 1 we built ephemeral execution - bounded, private, self-cleaning async workflows. In Part 2 we turned that into a reusable library with…

Building a Reusable Ephemeral Execution Library

In Part 1: Fire and Don't Quite Forget, we explored the theory behind ephemeral execution - bounded, private, debuggable async workflows that remember just enough to be useful and then evaporate. This article turns that pattern into a reusable library you can…

Fire and Don't Quite Forget - Ephemeral Execution Without State

Most async systems either remember too much (logs, queues, persisted junk you never wanted)… or they remember nothing at all (fire-and-forget black holes that vanish the moment something goes wrong). This article introduces something different: A pattern where…

Learning LRUs - When Exceeding Capacity Makes Your System Better

Most systems degrade when overloaded. Memory fills up, queries slow down, users complain, servers crash. A few unusual ones get better. This article shows how an LRU-based behavioural memory becomes self-optimising when it hits capacity - and how this pattern…

Cooking with DiSE (Part 4): Building Systems That Learn, Adapt, and Evolve

Most software architectures assume the system is static. DiSE assumes the system is alive. Note: This is Part 4 in the "Cooking with DiSE" series. See Part 1, Part 2: Graduated Apprenticeships, and Part 3: Untrustworthy Gods for background. This article is the…