Why .NET 10 Makes Modular Monoliths More Viable Than Microservices
Jan 24 · 7 min read · Microservices were never meant to be the default starting point. They were a response to a very specific set of problems, large teams, independent deployment requirements, organisational scaling, and systems that had already outgrown a single codebas...
Join discussion
Part 10. Migrating a Legacy Layered .NET Application to a Modular Monolith
Jan 22 · 5 min read · Most Development Teams do not wake up one morning with the freedom to design a modular monolith from scratch. They inherit something. A system that grew organically. A codebase that made sense at the time. Controllers, services, repositories, a share...
Join discussion
Part 9. Operational Concerns in Modular Monoliths
Jan 22 · 4 min read · There’s a point in every system’s life where architecture stops being something you reason about and starts being something you experience. It usually arrives during an incident, when logs are noisy, alerts are firing, and someone asks a deceptively ...
Join discussion
Part 7. Knowing When Your Modular Monolith Is Ready to Split
Jan 22 · 4 min read · By the time you ask whether a modular monolith should be split, you already know the system well enough that the question feels uncomfortable. If it feels academic, you’re not ready. The moment it becomes emotionally charged, when people disagree str...
Join discussion
Part 5. Authorisation as a Cross-Cutting Concern Without Leaking Modules
Jan 22 · 8 min read · If you’ve followed this series so far, you’ve done the hard structural work. You’ve enforced real module boundaries.You’ve organised behaviour into vertical slices.You’ve isolated data with separate DbContexts.You’ve stopped modules from chatting lik...
Join discussion
Part 2. Vertical Slice Architecture Inside a Modular Monolith
Jan 21 · 8 min read · In the first post of this series, I talked about enforcing real module boundaries. Assemblies. Internals. Contracts. The boring but essential stuff that stops your modular monolith collapsing into a shared-nothing-in-name-only mess. But once you’ve d...
Join discussion
Part 1. Enforcing True Module Boundaries in a .NET Modular Monolith
Jan 21 · 9 min read · There’s a moment that happens to most of us at some point in our careers. You’ve done “everything right”. You’ve split the solution into folders called Modules. You’ve got namespaces that look clean. You might even have separate projects. And yet, si...
Join discussion
Part 3. Multiple DbContexts per Module Without Breaking Transactions
Jan 21 · 9 min read · By the time you’ve enforced real module boundaries and organised behaviour using vertical slices, you run head-first into the next uncomfortable question: If modules are truly independent, why are they still sharing a DbContext? This is where most ...
Join discussion
Living Architecture - Crafting Code that Thrives with Us
May 14, 2025 · 6 min read · „I should do better.“ „There has to be a smarter way.“ „We need a full rewrite.“ „Let’s switch to microservices.“ Sound familiar? Wall of entanglement Most of us who create software have hit a wall — or several — and found ourselves like this. Th...
Join discussion