Technical blog
Posts
Thoughts, experiments, and practical lessons from building distributed systems with .NET and Azure.
- Problems first the trade-off, before the technology
- Close to the code what production actually teaches
- Proven by building decisions you can still defend
-
Microsoft Foundry Agents: From First Agent to Production Architecture
A Foundry prompt agent can advise on a failed Service Bus message, but instructions do not give it a way to dead-letter that message.
-
Chunking Is an Architectural Decision
Part 5 left the system with a document it was willing to keep.
-
RAG Starts With Ingestion, Not Chat
Someone adds a vector database in the middle, and the article moves on.
-
The First Architectural Decision Wasn't About AI
If the API knows about the database, the application knows about HTTP, and the domain knows about infrastructure, technical decisions start leaking across the …
-
How Many Consumers Do We Actually Need?
Imagine a queue of notifications waiting to be processed.
-
The Shape of the System
The first two articles in this series were about why I chose RAG and why I wanted to build a reference implementation in the first place.
-
Why I Chose RAG as My First Reference Implementation
After publishing the manifesto, one question appeared almost immediately.
-
Architecture Is Easy Until You Have to Build It
There is no shortage of articles about software architecture.
-
AI-first architecture for essential systems: what actually changes
AI is already part of software delivery. Developers use it to generate code, write tests, understand legacy code and speed up routine work. That is no longer …
-
A Hard Terraform Lesson: When a Terraform Refactor Tried to Destroy Production
While working on our infrastructure, I proposed a cost optimization around Azure Container Registry (ACR). The decision was a classic architectural trade-off: …