Recurring billing looks like a cron job that charges a card once a month. Then a customer upgrades on day 20, a card declines, and someone overpays. Here is how the hard parts actually work in .NET.
Recurring EU billing does not require a US payment gateway. Here is how a provider-agnostic design collects a finalized invoice over SEPA — no Stripe, no Mollie, no Cloud Act exposure — and stays retry-safe end to end.
You do not need a metering vendor to bill on usage. Here is the full in-process pipeline — event ingest, idempotent dedupe, watermark rollup, quota alerts, invoice — built on Granit.Metering and Granit.Invoicing.
Row-level, schema-per-tenant, or database-per-tenant? Here is how the three isolation strategies trade off — and how Granit gives you the safe default plus a mechanical path to strict isolation when a customer demands it.
Most .NET teams reach for a Python or Node sidecar the moment a device starts speaking MQTT. Here's how to keep the entire pipeline — broker connection, dedup, thresholds, time-series storage — in .NET 10, and why that stops being optional past 10 million rows a day.
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.
A server restart between your database commit and your HTTP POST drops the event forever. The fix is the transactional outbox pattern — persist the event in the same transaction as your data, relay it asynchronously, retry on failure. Here is how Granit.Webhooks implements it end-to-end.
Your strict Content Security Policy breaks the moment one ASP.NET Core route serves HTML — Scalar, an admin page, a Keycloak iframe. The usual band-aid weakens every other endpoint. Granit's per-endpoint CSP composition keeps strict defaults strict and lets the package that mounts the UI declare its own relaxation.
Prototype with Channel
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.
Every SaaS eventually needs invoices, contracts, monthly reports. The HTML-to-PDF route is cheaper, more flexible and easier to maintain than iText or QuestPDF — provided you build the pipeline right. Here's how.
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.
One PublishAsync call, nine delivery channels. How Granit fans out a single notification to email, SMS, WhatsApp, mobile push, web push, SignalR, SSE, Zulip, and the in-app inbox without rewriting your domain code.
Two-tier caches are fast, but cross-pod invalidation is the part everyone gets wrong. Here is how the L1 + L2 + backplane pattern works, and how Granit wires it up with Redis.
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.
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 the Granit codebase.
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.
SSE, SignalR, or raw WebSockets? A practical decision framework for .NET real-time applications, with protocol deep-dives, trade-offs, and ready-to-use Granit code samples for each transport.
FullStackHero and Granit both target modular .NET applications, but their architectures, compliance stories, and extension models diverge sharply. Here is a fair, side-by-side comparison for architects choosing their next foundation.
The new Granit.Mcp module family wraps the MCP C# SDK to expose your application capabilities to AI agents, with auto-discovery, RBAC authorization, and GDPR-compliant output sanitization.
Your React app stores access tokens in localStorage. A compromised npm package reads them. Game over. Granit.Bff moves token handling to the server, so the browser only sees an HttpOnly cookie it cannot read.
Granit ships 400+ NuGet packages with zero circular dependencies, enforced by Kahn's algorithm at startup and architecture tests at build time.
Granit is an open-source modular framework for .NET 10 — 400+ packages, zero circular dependencies, GDPR and ISO 27001 compliance built in. Here is why we built it and what it gives you.
Shared DbContexts create hidden coupling between modules. Here is how Granit enforces database isolation per module — and why it makes microservice extraction mechanical.
Microservices are not a goal. They are a trade-off. Here is why Granit bets on the modular monolith as the default architecture — and how the framework makes extraction painless when the time comes.
