Every chat, dashboard, or CMS eventually needs a green dot next to a name. Most teams build it twice: once for “is this person online”, once for “who else is looking at this document” — and get the multi-tab and multi-pod edge cases wrong both times. Here’s the primitive that replaces both.
Prototype with Channel
Every line-of-business app eventually grows an “import CSV” button. Done wrong it OOMs on the first 100k row file. Done right it streams, validates, resolves identity, and hands the user a correction file for the rows that failed.
Stop sprinkling CreatedAt assignments across repositories and IsDeleted = false across queries. Five interceptors and one global filter make compliance the default — and ExecuteUpdate the only thing left to watch for.
Hangfire ships fast. Then production scales out, two nodes fire the same recurring job at the same time, the outbox you bolted on doesn’t include the job table, and the audit log goes sideways. There is a better default in 2026.
LaunchDarkly is great. €0.0050 per MAU is less great when you have 200k tenants and want to gate “VideoConference” behind the Premium plan. Here is how to build LaunchDarkly’s core value in your own .NET codebase — without the bill.
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.
From accidental client evaluation to N+1 queries and tracked reads, these are the five EF Core anti-patterns that turn 50 ms endpoints into 5-second ones — and the exact fix for each.
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.
MediatR is in-process only — no outbox, no retry, no transport. Wolverine is the CQRS bus most teams actually need. Here is how Granit uses it.
EF Core InMemory and SQLite lie about PostgreSQL. Use Testcontainers to run ephemeral real databases in your integration tests — zero mocks, zero surprises in prod.
Wire Serilog, OpenTelemetry and the Grafana LGTM stack into a .NET 10 app in one call. Structured logs, distributed traces, metrics — all OTLP, all sovereign.
IOptions, IOptionsSnapshot, and IOptionsMonitor solve different problems. Picking the wrong one causes stale config, unnecessary allocations, or subtle concurrency bugs. Here is when to use each — with real examples from Granit’s 128 packages.
Hardcoded connection strings and static API keys are a breach waiting to happen. HashiCorp Vault gives you dynamic credentials, transit encryption, and per-entity key isolation — and Granit integrates all three as a single module dependency.
A dropped connection, a mobile retry, a load-balancer timeout — any of these can duplicate a POST. Idempotency keys turn dangerous replays into harmless no-ops, and Granit ships the entire pattern as a single middleware.
Stop returning bare strings from your .NET APIs. RFC 7807 Problem Details is the standard for error responses — here is why it matters, what the spec actually says, and how Granit enforces it with zero boilerplate.
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.
Returning EF Core entities directly from your endpoints leaks internal structure, creates circular references, and exposes sensitive data. Use response records instead.
Manual null checks are noisy and inconsistent. .NET provides built-in guard methods that are cleaner, faster, and throw the right exceptions every time.
new Regex(…, RegexOptions.Compiled) allocates at startup and hides patterns from the JIT. Source-generated regex is faster, safer, and enforced at build time.
DateTime.Now makes your code untestable and timezone-fragile. Here is how to replace it with TimeProvider and IClock for deterministic, test-friendly time.
