Should You Split That Into Microservices? Ask These 5 Questions First
Nobody regrets microservices on day one. The regret shows up eighteen months later, when the team is drowning in distributed-systems problems they nev...
Page 2 of 22. Practical .NET and software architecture lessons.
Nobody regrets microservices on day one. The regret shows up eighteen months later, when the team is drowning in distributed-systems problems they nev...
I just shipped Katabench, and it's the most fun system I've ever built: it takes C# from strangers and runs it safely on servers I own. Three Hetzner ...
This website ran on Netlify for years, at $19 a month. Earlier this month I moved it to Cloudflare Pages: same repo, same GitHub Actions pipeline, zer...
The most common question I get about vertical slice architecture isn't about structure. It's "where do my tests go?" The layered-architecture testing ...
Most of what runs on your servers was never meant to be public: databases, dashboards, admin panels, internal APIs. Tailscale connects your machines i...
NATS almost never comes up when .NET developers talk about message queues, and that's a shame. It's a tiny, fast, single-binary broker, and JetStream ...
We built the system exactly the way a modular monolith is supposed to be built, and that's how I ended up with two modules I couldn't pull apart a yea...
Long-running business processes are hard to get right. Dapr Workflow lets you write them as plain C# code that survives crashes and restarts, and Aspi...
DRY was never about code that looks the same. It's about knowledge. Most of the tangled abstractions I've had to unwind started as a well-meaning atte...
For years we faked union types with marker interfaces, base classes, and the OneOf library. C# 15 finally bakes them into the language - and here's a ...
Join 66,000+ readers of The .NET Weekly for practical tips and resources to improve your .NET and software architecture skills.