Skip to content
Granit
Blog

Core Concepts — Modules, DI & Architecture

Granit is not a collection of independent utilities. Every design decision flows from a small set of principles: modules compose with explicit dependency declarations, data is always scoped to its tenant, events cross boundaries without coupling, and compliance is structural rather than bolted on.

Understanding these concepts gives you the mental model to use Granit effectively and extend it without surprises.

How concepts connect

Section titled “How concepts connect”
graph TD
    MS[Module System] --> DI[Dependency Injection]
    DI --> Config[Configuration]
    DI --> P[Persistence]
    P --> CQRS[CQRS]
    P --> MT[Multi-Tenancy]
    P --> C[Compliance]
    CQRS --> C
    MS --> Msg[Messaging]
    Msg --> CQRS
    Msg --> WO[Wolverine Optionality]
    Msg --> C
    MT --> SM[Security Model]
    SM --> C

Start with the Module System — every other concept builds on it.

Core architecture

Section titled “Core architecture”
  • Module System — [DependsOn], topological sort, conditional modules, two-phase lifecycle
  • Dependency Injection — module service registration, Options pattern, PostConfigure
  • Configuration — Options (startup), Settings (runtime), Module Config (frontend read-only)

Data and infrastructure

Section titled “Data and infrastructure”
  • Persistence — isolated DbContext, interceptors (audit, soft delete, versioning), automatic query filters
  • CQRS — Reader/Writer separation, compliance-driven data access, least-privilege injection
  • Multi-Tenancy — three isolation strategies, transparent query filters, async-safe tenant context
  • Messaging — domain events, integration events, transactional outbox, automatic context propagation
  • Wolverine Optionality — Channel fallback, crash behavior, when you actually need a message bus

Security and compliance

Section titled “Security and compliance”
  • Security Model — JWT authentication, provider-agnostic RBAC, per-role caching, back-channel logout
  • Compliance — GDPR and ISO 27001 enforcement as structural patterns

Architecture

Section titled “Architecture”
  • Framework vs Modules — classification boundary and dependency rules between horizontal framework and vertical business modules

Tooling

Section titled “Tooling”
  • Bundles — meta-packages and the fluent GranitBuilder API for quick onboarding

Architecture decisions

Section titled “Architecture decisions”