Skip to content
fullstackhero

Architecture overview

FullStackHero is organized as a modular monolith: shared infrastructure in BuildingBlocks, vertical slices in Modules.*, and host applications under Playground.

Building blocks

Section titled “Building blocks”
  • Core – domain primitives, base types, exceptions, domain events.
  • Persistence – EF Core helpers, options, interceptors, and DbContext bindings.
  • Web – host wiring, middleware, versioning, OpenAPI, HTTP pipeline helpers.
  • Caching / Jobs / Mailing / Storage – optional cross-cutting infrastructure.

These projects are referenced by modules and hosts, not the other way around.

Feature modules

Section titled “Feature modules”

Each feature module (for example, Identity, Multitenancy, Auditing) has:

  • A runtime project (Modules.X) with endpoints, handlers, and services.
  • A contracts project (Modules.X.Contracts) with DTOs and integration contracts.

Architecture tests constrain which projects can reference which, protecting boundaries as the solution grows.