Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · Vertical Slice Architecture (C#, .NET, MediatR, PostgreSQL, Docker)
stack-profile:vertical-slice-architecturea5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewjsongraph
II.
StackProfile overview

stack-profile:vertical-slice-architecture

Reference · live

Vertical Slice Architecture (C#, .NET, MediatR, PostgreSQL, Docker) overview

A C# application organized by feature slices rather than technical layers, where each vertical slice contains its own handler, validation, data access, and response mapping. MediatR dispatches commands and queries to their respective slice handlers, eliminating cross-cutting service classes that bloat traditional layered architectures. Entity Framework Core provides PostgreSQL access, FluentValidation enforces input rules per-slice, and AutoMapper handles DTO projection. Docker containers target the .NET runtime. The tradeoff is code duplication across slices and the need for team discipline to avoid slices growing into mini-monoliths, but the pattern excels at enabling parallel feature development.

StackProfileOutgoing · 21Incoming · 0

Attributes

displayName
Vertical Slice Architecture (C#, .NET, MediatR, PostgreSQL, Docker)
description
A C# application organized by feature slices rather than technical layers, where each vertical slice contains its own handler, validation, data access, and response mapping. MediatR dispatches commands and queries to their respective slice handlers, eliminating cross-cutting service classes that bloat traditional layered architectures. Entity Framework Core provides PostgreSQL access, FluentValidation enforces input rules per-slice, and AutoMapper handles DTO projection. Docker containers target the .NET runtime. The tradeoff is code duplication across slices and the need for team discipline to avoid slices growing into mini-monoliths, but the pattern excels at enabling parallel feature development.
composes
  • language:csharp
  • library:aspnet-core
  • library:mediatr
  • library:entity-framework
  • library:fluentvalidation
  • library:automapper
  • library:xunit
  • tool:dotnet-cli
  • tool:docker

Outgoing edges

applies_to2
  • domain:software-engineering·DomainSoftware Engineering
  • domain:backend·DomainBackend
composed_of9
  • language:csharp·LanguageC#
  • library:aspnet-core·LibraryASP.NET Core
  • library:mediatr·LibraryMediatR
  • library:entity-framework·LibraryEntity Framework Core
  • library:fluentvalidation·LibraryFluentValidation
  • library:automapper·LibraryAutoMapper
  • library:xunit·LibraryxUnit.net
  • tool:dotnet-cli·Tool.NET CLI
  • tool:docker·ToolDocker
follows_workflow2
  • workflow:feature-development·Workflow
  • workflow:architecture-decision·WorkflowArchitecture Decision
requires_skill_area5
  • skill-area:domain-driven-design·SkillAreaDomain-Driven Design
  • skill-area:backend-api-design·SkillAreaBackend API Design
  • skill-area:object-relational-mapping·SkillAreaObject-Relational Mapping (ORMs)
  • skill-area:unit-testing·SkillAreaUnit Testing
  • skill-area:data-validation-sanitization·SkillAreaData Validation and Sanitization
used_by_role3
  • role:backend-engineer·RoleBackend Engineer
  • role:architect·RoleArchitect
  • role:tech-lead·RoleTech Lead

Incoming edges

None.

Related pages

No related wiki pages for this record.

Shortcuts

Open in graph
Browse node kind