Clean Architecture Manga: a .NET 6 wallet split into use cases, presenters and adapters
:cyclone: Clean Architecture with .NET6, C#10 and React+Redux. Use cases as central organizing structure, completely testable, decoupled from frameworks
At a glance
- What is it?
- ivanpaulovich's clean-architecture-manga builds a virtual wallet organized around use cases as the central structure. It runs as a Docker bundle with Identity Server, SQL Server and a React client.
- Who is it for?
- Adopt this repository if you want a readable reference for how use cases, presenters, ports and adapters fit together in one C# solution, and if Docker, SQL Server and a self-signed certificate on wallet.local are acceptable in your environment. Do not adopt it as a starting template for production: the README presents it as a sample implementation.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 146 days ago.
- What is it written in?
- Mainly C#, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ivanpaulovich/clean-architecture-manga4,386 ★ · +16
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| ivanpaulovich/clean-architecture-manga | 4.4k | 4.4k |
16 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Every Register and Withdraw step has its own folder, interfaces and presenter
Most .NET samples start from an entity model and let services hang off it. This one inverts that. The README states the intent plainly: use cases as the central organizing structure, decoupled from frameworks and technology details, built by small components that are developed and tested in isolation. That is the whole pitch, and it is aimed at engineers who already know what a controller is and want to see where the coupling actually goes. It is not aimed at teams looking for a feature-rich wallet.
Hexagonal, onion and clean architecture share one repository
The wiki index carried by the README treats three architecture styles as siblings rather than rivals. Ports and adapters is described through ports, adapters, the left side and the right side. Onion and Clean Architecture get their own entries. Design Patterns then names Controller, ViewModel, Presenter, Unit of Work, First-Class Collections and Factory, and a second block of domain-driven patterns leads with Value Object. One repository demonstrating three vocabularies for the same dependency rule is either a strength or an ambiguity, depending on what you came for. If you want one correct answer, the use case structure in the main branch settles it. If you are comparing styles, the wiki pages are the comparison.
The presenter turns domain output into Standard, Error or Alternative results
The design pattern index splits presenter output into three named kinds: Standard Output, Error Output and Alternative Output. That split is the concrete difference from an MVC controller in this sample. A controller maps a request to a view model and returns; a presenter receives the use case result and decides how it becomes something the client can consume. With three output paths, the error branch does not have to be modelled as a failure of the whole action. Read the presenter pages first when you are reading the code, because that is where the sample departs from what most controllers written for .NET 6 look like. Unit of Work and First-Class Collections appear alongside.
One setup script brings up NGINX, three apps and SQL Server
There is no package-by-package install. The whole solution starts from a script in the .docker directory, and which one you run depends on your shell. On macOS:
$ cd .docker && ./setup.shOn Windows PowerShell:
PS cd .docker && ./setup.ps1After it finishes, the README says the following containers should be running when you list them:
docker psFive rows of the expected result are worth keeping in mind: NGINX and the Wallet SPA both answer on https://wallet.local:8081, the Accounts API answers on https://wallet.local:8081/accounts-api, Identity Server answers on https://wallet.local:8081/identity-server, and the database connection string is Server=localhost;User Id=sa;Password=<YourStrong!Passw0rd>;Database=Accounts;. Open that URL, click Log In, and accept the self-signed certificate when the browser asks. The client is a separate application in the repository, wallet-spa, which is why identity-server and nginx have their own top-level folders.
Three branches carry three framework targets under one use case structure
The main branch is .NET 6. The dotnet5.0 branch is .NET 5. The dotnet3.1 branch is .NET Core 3.1. The README calls these supported versions, but each branch sits on a different year of framework support, so pick yours before you read any code: C# syntax and the project file targets differ between them. A reader arriving at the .NET Core 3.1 branch will find a sample that predates records, and copying its patterns into a .NET 6 project means translating them by hand.
Branch choice also decides how much code you inherit. The repository is not archived and the last push was on 2026-06-22, yet the newest tag is v1.0.0 from 2018-04-23, so anyone pinning to a release gets a 2018 snapshot while anyone cloning gets the current tree. The main branch is the one to study if your own services are on .NET 6.
Where the sample stops being usable
Four things break before the architecture does. Running the setup script needs Docker and a working wallet.local mapping, which is why the README tells you to click through a certificate warning; on a machine without those, nothing starts and the error will come from Docker or the browser, not from the sample. SQL Server is a licensed product and the connection string in the README uses the sa account, so the setup is a developer workstation arrangement, not a deployment story. The wallet itself is deliberately thin: register an account, then Deposit, Withdraw and Transfer against the balance. Use cases as organizing structure also means the ceremony is real: every new behaviour means a new use case folder, its interfaces and its presenter, which is the correct trade-off for a teaching sample and a slow one for a team shipping weekly. The repository is licensed Apache-2.0, which permits reuse in your own project subject to its notice and patent terms; read the LICENSE file before you copy anything.
Ardalis templates make the same bet without the Docker bundle
Clean Architecture Ardalis takes the same dependency rule and packages it as a template rather than a story. The difference in approach is what you start from. This repository gives you a running wallet with a React client, Identity Server and SQL Server, so you read the flow of control in the context of an application that does something. A template gives you a bare skeleton with the layers present and nothing in them, so you read the structure without the distraction of a domain. Both leave the same bill for the same idea: every feature is a use case plus its presenter plus its interfaces. If you want to see the shape inside something that runs, this one. If you want the shape in your own solution with nothing inherited, the template.
Editorial conclusion
Adopt this repository if you want a readable reference for how use cases, presenters, ports and adapters fit together in one C# solution, and if Docker, SQL Server and a self-signed certificate on wallet.local are acceptable in your environment. Do not adopt it as a starting template for production: the README presents it as a sample implementation. Before anything else, run the setup script for your operating system and check that the four application containers come up on https://wallet.local:8081 and that SQL Server is running.
Frequently asked questions
How do I run the Clean Architecture Manga sample locally?
Run the setup script from the .docker directory, ./setup.sh on macOS or ./setup.ps1 in Windows PowerShell. Then confirm with docker ps that NGINX, the Wallet SPA, the Accounts API, Identity Server and SQL Server are running, and browse to https://wallet.local:8081 and click Log In.
Which .NET version does Clean Architecture Manga support?
Three, each on its own branch: .NET 6 on main, .NET 5 on the dotnet5.0 branch and .NET Core 3.1 on the dotnet3.1 branch. Read the code from the branch that matches the target framework of your own project.
What is a use case in Clean Architecture Manga?
Use cases are the central organizing structure of the sample, decoupled from frameworks and technology details. The README names Register Flow of Control and Get Customer Details Flow of Control as the worked examples.
Can I use this code in a commercial project?
The repository is licensed Apache-2.0, which allows reuse in your own project provided you follow the notice and licence terms in the LICENSE file. Read those terms yourself before shipping the code.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ivanpaulovich-clean-architecture-manga)Star history chart for your README
[](https://hysenlabs.com/projects/ivanpaulovich-clean-architecture-manga)Was this useful?