hexagonal-architect

To structure a .NET app with hexagonal architecture, you separate concerns across Domain, Application, Adapters, and API layers using Ports and Adapters. This enforces strict dependency rules so core domain logic remains isolated from infrastructure changes.

You implement CQRS by using MediatR-based handlers for command and query dispatch within the Application layer, while applying FluentValidation to enforce business rules and FluentResults to handle execution outcomes and return Result objects.

Yes, hexagonal architecture supports Azure Functions patterns by wrapping them as infrastructure adapters. It includes specific sub-skills for service bus and storage integrations, ensuring cloud functions connect to core domain logic through defined ports.

The best way to handle errors in a .NET clean architecture solution is using FluentResults to return Result objects instead of throwing exceptions. This pattern propagates validation failures from FluentValidation through MediatR handlers to the API layer cleanly.

Implementing ports and adapters in .NET involves supporting sub-skills for repository adapters, auditing, and infrastructure setup. These components manage data persistence and track changes while maintaining strict boundary rules between application and infrastructure layers.

You should avoid hexagonal architecture for simple .NET applications or prototypes where strict layering, CQRS, and MediatR overhead outweigh the benefits. It is designed for scalable, complex domains requiring long-term maintainability and heavy testing.