Tag feed

#modular-monolith

26 posts1 followers

Explore Hashnode

Alternatives

Trending tags this week

USUsman Soliucode-along.hashnode.devJun 13 · 29 min read

From Monolith to Microservices

Most systems don't start as microservices. In fact, many of the products we use every day began as a single application connected to a single database. That is usually the right decision. Yet, if you

0

PKPatrick Kearnsfullstackcity.comMar 12 · 10 min read

Communicating Between Modules in a Modular Monolith

Why Developers Get This Wrong Most engineers learning modular monoliths fall into two traps. The first group collapses boundaries by sharing DbContexts, repositories, and entities across modules. The

0

PKPatrick Kearnsdotnetdigest.comJan 24 · 7 min read

Why .NET 10 Makes Modular Monoliths More Viable Than Microservices

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...

0

PKPatrick Kearnsfullstackcity.comJan 22 · 5 min read

Part 10. Migrating a Legacy Layered .NET Application to a Modular Monolith

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...

0

PKPatrick Kearnsfullstackcity.comJan 22 · 4 min read

Part 9. Operational Concerns in Modular Monoliths

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 ...

0

PKPatrick Kearnsfullstackcity.comJan 22 · 4 min read

Part 7. Knowing When Your Modular Monolith Is Ready to Split

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...

0

PKPatrick Kearnsfullstackcity.comJan 22 · 8 min read

Part 5. Authorisation as a Cross-Cutting Concern Without Leaking Modules

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...

0

PKPatrick Kearnsfullstackcity.comJan 21 · 8 min read

Part 2. Vertical Slice Architecture Inside a Modular Monolith

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...

0

PKPatrick Kearnsfullstackcity.comJan 21 · 9 min read

Part 1. Enforcing True Module Boundaries in a .NET Modular Monolith

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...

0

PKPatrick Kearnsfullstackcity.comJan 21 · 9 min read

Part 3. Multiple DbContexts per Module Without Breaking Transactions

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 ...

0

#modular-monolith

Search Hashnode

#modular-monolith

Explore Hashnode

Trending tags this week

From Monolith to Microservices

Communicating Between Modules in a Modular Monolith

Why .NET 10 Makes Modular Monoliths More Viable Than Microservices

Part 10. Migrating a Legacy Layered .NET Application to a Modular Monolith

Part 9. Operational Concerns in Modular Monoliths

Part 7. Knowing When Your Modular Monolith Is Ready to Split

Part 5. Authorisation as a Cross-Cutting Concern Without Leaking Modules

Part 2. Vertical Slice Architecture Inside a Modular Monolith

Part 1. Enforcing True Module Boundaries in a .NET Modular Monolith

Part 3. Multiple DbContexts per Module Without Breaking Transactions