Find your next readFilters
Reset

Page 4 of 5 (Total items: 46)
Why You Probably Shouldn't Use Microservices (Yet)

Microservices have become the default "serious system" architecture. If you want to sound mature, you talk about service meshes, event buses, distributed tracing, and "independent deployability". If you want to look enterprise-ready, you draw boxes until the…

Why I Don't Use LangChain (and What I Do Instead)

I'm a .NET developer. When I started building LLM-powered systems, everyone pointed me toward LangChain. "It's the standard," they said. "All the examples use it." And they were right - if you're in the Python ecosystem, LangChain is everywhere. But here's the…

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…

Modern CQRS and Event Sourcing in .NET: Doing It Properly

NOTE: This is an old article I forgot to release. Here it is, enjoy! I updated it but may be some issues I missed. CQRS and Event Sourcing - two patterns that are often mentioned together but frequently misunderstood. In this article, I'm going to show you how…

The most half assed, ill informed article I've ever read on .NET

http://rss.com.com/2010-7345_3-5079603.html?part=rss&tag=feed&subj=news Gotta love this quote... "Unlike J2EE middleware, .Net doesn't do much beyond connecting information to the Windows desktop. Companies have moved beyond merely connecting applications but…

Futher to my earlier rant...

I wrote here complaining about the (in my opinion) pretty poor treatment of Architecture (especially) for ASP.NET. Well, here's a suggestion of a solution - I've just read the whitepapers for ALL of the starter kits - some people have mailed me to say that…

Page 4 of 5 (Total items: 46)
logo

© 2026 Scott Galloway — Unlicense — All content and source code on this site is free to use, copy, modify, and sell.