#Clean-Architecture
7 notas · última:
Unit Testing Clean Architecture Use Cases
The article shows how to unit test a Clean Architecture use case by mocking dependencies, covering failure and success paths, checking exception propagation, and keeping time-dependent code testable.
Building Your First Use Case With Clean Architecture
The article explains how a user-registration use case fits in the Application layer, depends on interfaces for external systems, and follows the dependency rule while remaining testable.
Don't use MediatR by default on all .NET projects
The text argues that MediatR should not be added by default to every .NET project: the choice depends on the use case, and using internal messaging in dependent contexts can create unnecessary complexity.
Finding the Right Balance Between DDD, Clean and Hexagonal Architectures
The article argues for a practical mix of Clean Architecture, DDD and Hexagonal Architecture, keeping domain logic isolated, favoring immutable domain objects, and avoiding boilerplate that adds little value.
How To Implement a TypeScript Web App With Clean Architecture
The article explains how to structure a TypeScript web app with core, data, presentation, and DI layers so logic stays independent of frameworks, storage, and other details.
Clean Architecture With .NET 6 Using Entity Framework
The article shows how to add Entity Framework to a .NET 6 clean architecture solution, define an AppSetting entity, wire an application DB context through dependency injection, and create the database with migrations.
Evolving modular monoliths: 1. An architecture for .NET
The article introduces a modular monolith approach for .NET that keeps monolith simplicity while isolating features with bounded contexts, layered design, and rules that improve cohesion, testability, and changeability.