Architecture, drawn out
A diagram-native publication on software architecture — the systems, the trade-offs, and the diagrams that make them legible.
An opinion on why the "I" prefix convention for C# interfaces exists, where it causes harm, and what better naming discipline actually looks like in practice.
Three progressively better approaches to injecting specific interface implementations into particular services using ActivatorUtilities, without registering concrete types in the DI container.
A structured approach to software architecture using vision, boundaries, and contracts as the three pillars of design, with practical tooling examples from wiki to prototype.
A producer publishes to a broker topic that fans out to independent consumers, with a dead-letter queue for poison messages.
Silo, bridge, and pool strategies for isolating tenant data, and the cost/isolation trade-off each one makes.
How an authorization request travels from the client through the gateway and payment service to the acquirer and card network, and how the result returns.
Architecture is such a loaded word.
It can be applied to everything in our world and describes the structure that holds an idea, principle, system, process, or organization together. It is all the contracts (agreements) between all parts to form a foundation.
Walls are the parts that defines the structure (architecture). But the room is the function. The furniture is the use case. Structure determines what is possible.
Office hours
A recurring open session to pressure-test one real architecture. Bring a diagram and the decision that's keeping you up at night.
Next session
Office-hours details