Page 3 of 20.
Modern technology operates in a paradox. Our tools have never been more powerful, yet our systems have never felt more fragile. Every framework, pipeline, and process…
Your domain model exists to protect your business rules. Your API exists to protect your clients. When you expose EF Core entities directly from your ASP.NET Core…
If your default move for “modern UX” is a SPA, you are paying a tax you do not need. You pay for it in build pipelines, duplicated validation rules, fragile client…
If every controller in your system does its own authentication, logging, and error handling, you do not have an architecture. You have a crowd of small frameworks…
If a single endpoint pulls half your database just to render a small card on a mobile screen, your problem is not the database. Your problem is that you are afraid to…
If one customer quietly turns into three different in-memory objects during a single request, your domain is already lying to you. You see it when: - Different parts of…
If a single business operation calls SaveChangesAsync three times, you do not have a transaction. You have a sequence of partial commits that you hope never fails in the…
If DbContext shows up in every corner of your codebase, you do not have a domain model. You have a thin layer of LINQ wrapped in HTTP. You see it when: - Minimal API…
If every interesting class in your system secretly knows a connection string, your domain is not a model. It is a thin layer of code on top of a data access layer. You…
Sometimes, your domain is really just rows in a table. You have a Customers table with Id, Email, and CreditLimit. You load a row, tweak a field, and write it back. That…
This is my post for the 2025 C Advent. Check out all the great posts! I want to wish you a Merry Christmas, Happy Holidays, Happy Hanukkah, Happy Kwanzaa, and, finally…
Open a typical ASP.NET Core project, and you will often see the same shape: - Controllers that validate input, construct entities and call several repositories - Direct…
