Code reviews catch typos. They do not catch a controller quietly importing Microsoft.EntityFrameworkCore and bypassing your repository layer. Architecture tests do — at build time, on every PR. Here is a pragmatic playbook for .NET teams.
ASP.NET Core dropped the synchronization context years ago. So why do every Granit library and the .NET runtime itself still write ConfigureAwait(false) on every await? Because libraries do not get to choose their host.
Scattering validation across controllers, services, and entities produces inconsistent errors and missed cases. Pin it to the API boundary with FluentValidation and endpoint filters — and let the platform do the rest.
String interpolation in log calls allocates on every invocation, even when the log level is disabled. Source-generated [LoggerMessage] eliminates that cost entirely and gives you structured logs for free.
Granit ships 376 NuGet packages with zero circular dependencies, enforced by Kahn’s algorithm at startup and architecture tests at build time.
Manual null checks are noisy and inconsistent. .NET provides built-in guard methods that are cleaner, faster, and throw the right exceptions every time.
