Blog
Mert Özen's blog posts on software development, backend, frontend, and DevOps.
Finding Module Boundaries: Business Capabilities, Bounded Contexts and Data Ownership
Module boundaries are drawn by business capability and data ownership, not by technical layer: each bounded context becomes a module and each table gets exactly one writer. Using an EF Core interceptor in Bookstore we measure three modules writing to the Books table and two to Orders, show why the Book inside an Order must be a separate snapshot model, and list the symptoms of a wrong boundary.
Modular Monolith Solution Structure in .NET: Module Projects, internal and Module Registration
Each module gets two projects: a small Contracts project other modules can see and a Core project where everything is internal; the Host is just the composition root calling AddXModule() and MapXEndpoints(). We go from an empty solution to a running three-module Host, show with real CS0234/CS0122 errors where project references and internal protect the boundary and where they don't, and list concretely what may and may not go into the Shared Kernel.