rafaelfgx/Architecture

.NET 10, Angular 22, Clean Architecture, Clean Code, SOLID, KISS, DRY, Mediator Pattern, Folder-by-Feature Structure

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on October 8th, 2017
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 803
Total Stargazers: 3,277 (+0)
Total Subscribers: 264 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Architecture is a reference implementation demonstrating clean architecture principles for full-stack .NET and Angular applications.

The project addresses the challenge of building maintainable, scalable applications by implementing established architectural patterns and principles. It uses clean architecture layering, the mediator pattern for request handling, and a folder-by-feature structure to organize code by business capability rather than technical type. This approach centralizes cross-cutting concerns like validation, logging, and security into standardized flows, reducing duplication and cyclical dependencies while keeping individual components focused on single responsibilities.

Developers building enterprise .NET applications with Angular frontends should consider this project as a reference for structuring medium to large systems. The folder-by-feature organization suits teams wanting to avoid the fragmentation that comes from organizing by technical layer alone. The emphasis on avoiding unnecessary dependency injection and the result pattern for consistent error handling makes the codebase easier to test and reason about. This is particularly valuable for teams adopting SOLID principles and clean code practices but uncertain how to apply them concretely in a full-stack context.

The project maintains active build automation and provides multiple pathways for local development, including Docker support for simplified setup. The repository includes published packages available through standard package management channels, indicating ongoing maintenance and a commitment to making the architectural patterns reusable across projects.