CleanArchitecture.Extensions

Problem and Context

• Teams using Clean Architecture needed stronger cross-cutting primitives without forking template internals.
• Operational concerns such as validation, exception mapping, and caching behavior needed consistent package-level solutions.

Built

• MediatR behaviors for correlation logging, performance thresholds, validation, and exception mapping.
• Result primitives, guard clauses, deterministic clocks, cache keys, cache-aside helpers, and stampede protection.
• Docs, samples, symbols, SourceLink, CodeQL scanning, and automated package publishing.

Architecture

• Composition over intrusion: behaviors, guards, and adapters without handler rewrites.
• Options-first configuration and catalog-driven errors.
• Incremental adoption path for teams already using Clean Architecture.

Integrations

• NuGet distribution with SourceLink and symbols.
• CI/CD and CodeQL checks integrated into package release flow.

Reliability, Security, and Operations

• Deterministic clocks, result primitives, and guard helpers for predictable handler behavior.
• Cache-aside helpers and stampede protection to reduce production contention.

Operations

• NuGet publishing pipeline with semantic versioning.
• SourceLink and symbol packages for production debugging.
• Security scanning and CI gates.

Technology Stack