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.
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.
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.
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.
Build a complete CRUD module with Granit in under 10 minutes — from entity definition to validated endpoints with full audit trail and soft delete.
Shared DbContexts create hidden coupling between modules. Here is how Granit enforces database isolation per module — and why it makes microservice extraction mechanical.
