ivanpaulovich/clean-architecture-manga

:cyclone: Clean Architecture with .NET6, C#10 and React+Redux. Use cases as central organizing structure, completely testable, decoupled from frameworks

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 15th, 2026
Created on December 27th, 2017
Open Issues & Pull Requests: 45 (+0)
GitHub issues: Enabled
Number of forks: 752
Total Stargazers: 4,370 (+0)
Total Subscribers: 224 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Clean Architecture Manga is a reference implementation demonstrating clean architecture principles applied to a full-stack application built with .NET and React.

The project addresses the challenge of organizing code around business logic rather than technical frameworks. It structures the application with use cases as the central organizing principle, creating a layered architecture where domain logic remains independent of infrastructure concerns like databases, web frameworks, and UI libraries. This approach enables the core business rules to be tested and modified without coupling to external dependencies.

Developers should adopt this project as a learning resource or architectural template if they are building applications where testability and maintainability are priorities. It suits teams working with .NET and React who want to understand how to apply domain-driven design and SOLID principles in practice. The monorepo structure demonstrates how to organize multiple services and components while maintaining clean boundaries between layers. This is particularly valuable for those transitioning from framework-centric architectures to use-case-driven designs, or for teams establishing architectural standards across microservices.

The project shows consistent engagement with regular updates and refinements to its codebase. The repository maintains active documentation and examples that reflect current tooling practices. Development activity demonstrates attention to keeping the implementation aligned with evolving language features and framework versions. The project includes comprehensive test coverage throughout its layers, indicating a sustained commitment to demonstrating testability as a core architectural principle.