Practical.CleanArchitecture tags say .NET 9 while its description claims .NET 10
Full-stack .Net 10 Clean Architecture (Microservices, Modular Monolith, Monolith), Blazor, Angular 22, React 19, Vue 3.5, BFF with YARP, NextJs 16, Domain-Driven Design, CQRS, SOLID, Asp.Net Core Identity Custom Storage, OpenID Connect, EF Core, OpenTelemetry, SignalR, Background Services, Health Checks, Rate Limiting, Clouds (Azure, AWS, GCP), ...
At a glance
- What is it?
- Practical.CleanArchitecture is a C# reference repository for layered, hexagonal, onion and vertical-slice layouts, with monolith, modular monolith and microservice variants. Its newest release tag is v2025.11 for .NET 9 and Angular 20 while the repository description advertises .NET 10 and Angular 22, every configuration path it documents sits under src/Monolith, and the sample settings carry a literal sa password next to a gitleaks pipeline.
- Who is it for?
- Practical.CleanArchitecture is useful as a working catalogue of layouts rather than as a prescription, because the repository itself warns that the samples contain multiple ways of doing things and are not always best practice, and that framing turns out to be accurate.
- Can I use it commercially?
- Yes. MIT 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 received new commits within the last day.
- 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
- phongnguyend/Practical.CleanArchitecture2,465 ★ · +3
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| phongnguyend/Practical.CleanArchitecture | 2.5k | 2.5k |
3 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The blurb says .NET 10 and Angular 22, the newest tag says 9 and 20
The repository description is a single long inventory: .NET 10 Clean Architecture across microservices, modular monolith and monolith, Blazor, Angular 22, React 19, Vue 3.5, a BFF with YARP, NextJs 16, domain-driven design, CQRS, SOLID, ASP.NET Core Identity with custom storage, OpenID Connect, EF Core, OpenTelemetry, SignalR, background services, health checks, rate limiting, and Azure, AWS and GCP.
The release tags tell a different set of numbers. The newest is v2025.11, labelled .NET 9, Angular 20, React 19, Vue 3.5 and NextJs 15, dated 2025-11-13. Before it sit v2024.12 for .NET 8 with Angular 18, and v2023.12 for .NET 7 with Angular 16.
So the description and the tag history have drifted apart on the runtime and on two of the frontends, and the recorded last push is dated 2026-09-28, which is later than any tag. The tags also advance roughly yearly and on a year-month name, so this is a repository whose shape changes on a slow train rather than per release.
React 19 and Vue 3.5 are the two numbers the description and the newest tag agree on.
The sample settings carry an sa password, and gitleaks runs in the pipeline
The configuration section shows a `ConfigurationSources` block in which both sources are switched off, and the SQL Server entry contains a fully formed connection string:
"ConfigurationSources": {
"SqlServer": {
"IsEnabled": false,
"ConnectionString": "Server=127.0.0.1;Database=ClassifiedAds;User Id=sa;Password=sqladmin123!@#",
"SqlQuery": "select [Key], [Value] from ConfigurationEntries"
},
"AzureKeyVault": {
"IsEnabled": false,
"VaultName": "https://xxx.vault.azure.net/"
}
},The `sa` account and that literal password appear in four separate blocks across the section, since the reader is shown the disabled form, the enabled form, and two further variants. The RabbitMQ sample does the same thing with `UserName` set to `guest` and `Password` set to `guest`.
The repository also configures secret scanning. The top level holds a `gitleaks.toml` and an `azure-pipelines.gitleaks.yml`, so a scanner for committed credentials is wired into the build.
The samples are development placeholders pointing at 127.0.0.1, and the keys are real enough to be mistaken for working defaults. The shape of the block is what is worth copying.
The `ConfigurationSources` selector is also the one place where the switches are not exclusive. A fourth example enables the database and the key vault at the same time.
The same four events get differently joined queue names on each broker
Four message brokers are offered and each gets its own paste-in block. RabbitMQ, Kafka, Azure Queue Storage and Azure Service Bus. The event names are the same four in all of them: FileUploadedEvent, FileDeletedEvent, EmailMessageCreatedEvent and SmsMessageCreatedEvent.
The naming convention for those events is not the same across providers. The RabbitMQ block joins the prefix and the event name with a low line:
"RoutingKeys": {
"FileUploadedEvent": "classifiedadds_fileuploaded",
"FileDeletedEvent": "classifiedadds_filedeleted",
"EmailMessageCreatedEvent": "classifiedadds_emailcreated",
"SmsMessageCreatedEvent": "classifiedadds_smscreated"
}Azure Queue Storage uses hyphens for the same four names:
"QueueNames": {
"FileUploadedEvent": "classifiedadds-fileuploaded",
"FileDeletedEvent": "classifiedadds-filedeleted",
"EmailMessageCreatedEvent": "classifiedadds-emailcreated",
"SmsMessageCreatedEvent": "classifiedadds-smscreated"
}Kafka also uses the low-line form. So switching provider means the queue and topic names change shape, not just their host or credentials, and any consumer or dashboard built against the RabbitMQ spelling stops matching. The container key differs too, since RabbitMQ calls it RoutingKeys and the others call it QueueNames.
RabbitMQ additionally carries an `ExchangeName` set to `amq.direct`, which the other three do not have an equivalent for.
The Azure Key Vault field expects a vault URL
The key vault entry is the smallest of the configuration examples and the easiest to misread:
"AzureKeyVault": {
"IsEnabled": false,
"VaultName": "https://xxx.vault.azure.net/"
}Although the key is named `VaultName`, the application passes its value to `new Uri(...)` when constructing an Azure `SecretClient`. Supply the full URL of your own vault, such as `https://your-vault.vault.azure.net/`; `xxx` is only a placeholder. The application uses `DefaultAzureCredential`, so the selected identity must also have permission to read the required secrets.
The key vault source is only one half of the selector. It can be combined with the database source in the same block, which is the documented way to read settings from both places at once.
Two headings are empty, and the diagrams are the actual documentation
Before the configuration section, the README is a list of architecture headings. Database Centric against Domain Centric. Hexagonal. Onion. The Clean Architecture. Classic Three-layer. Modern Four-layer. Layer Dependencies. Layer Examples. Testing Pyramid. Vertical Slice Architecture for a modular monolith.
Every one of those ten is a heading followed by a single link, and each link opens draw.io with a percent-encoded raw file address pointing into `docs/imgs/` on the master branch. The diagrams are draw.io files, so the comparison the README is offering cannot be read as text in the repository.
Two headings then have nothing at all under them. Solution Structure is a heading with no body, and How to Run is a heading immediately followed by a subheading for updating configuration. Neither is expanded.
So the documented answer to how the solution is laid out, and to how to run it, is absent from the README, while the diagrams that are linked describe layer shapes rather than this repository's own directories. The default branch is master, and the diagram links are written against master.
The README opens with a warning that the code samples contain multiple ways and patterns to do things and are not always best practices or recommended for all situations. That instruction is the honest summary of the whole repository.
Every documented configuration path sits under src/Monolith
The description names three shapes: microservices, modular monolith and monolith. The configuration instructions cover one of them.
Every settings file named in the documentation sits under the Monolith folder. The MVC application's settings are at `src/Monolith/ClassifiedAds.WebMVC/appsettings.json`, the Web API's at `src/Monolith/ClassifiedAds.WebAPI/appsettings.json`, and the background worker's at `src/Monolith/ClassifiedAds.Background/appsettings.json`. The three configuration selectors are therefore all configured through the monolith host.
Those three projects also tell you what the monolith is made of: a server-rendered web front end, a separate Web API, and a background service host. The background service is the one that owns the `Messaging` section, which is consistent with a broker being consumed by whatever long-running work exists rather than by a request.
For someone taking the modular monolith or microservices layout, the settings have to be rediscovered from the source tree, because the paste-in blocks in the README are addressed to a different arrangement. The top level does carry `deployments/` and `tools/` directories, so the other shapes have supporting files, just no configuration walkthrough.
Storage switches by provider name, and the local sample is a Windows drive
Three storage backends sit behind one key. The `Storage` block has a `Provider` value, and setting it selects the implementation:
"Storage": {
"Provider": "Amazon",
"Amazon": {
"AccessKeyID": "xxx",
"SecretAccessKey": "xxx",
"BucketName": "classifiedadds",
"RegionEndpoint": "ap-southeast-1"
}
}Azure Blob is the second option, holding a connection string and a container name. The third is Local, whose sample path is a Windows drive letter:
"Storage": {
"Provider": "Local",
"Local": {
"Path": "E:\\files"
},
}A drive-letter path is the shape of a Windows default, and the Amazon sample pins a single region, ap-southeast-1, which is Singapore. Both are values a reader will inherit without thinking about them.
The same one-key pattern appears in messaging, where `Provider` takes RabbitMQ, Kafka, AzureQueue or AzureServiceBus, and in configuration sources, where each entry carries its own `IsEnabled` flag instead. Three selectors, two different conventions, and one of them non-exclusive.
Editorial conclusion
Practical.CleanArchitecture is useful as a working catalogue of layouts rather than as a prescription, because the repository itself warns that the samples contain multiple ways of doing things and are not always best practice, and that framing turns out to be accurate. Read the two version sources before you plan anything: the newest tag says .NET 9 with Angular 20, while the description says .NET 10 and Angular 22, so pick the one you will actually build against rather than the one the blurb advertises. Two more checks matter. Every configuration path in the documentation is under src/Monolith, so if you intend a modular monolith or microservices layout you are working without documented settings. And the sample settings contain a working sa password and a guest/guest broker pair, in a repository that runs gitleaks in Azure Pipelines, so copy the structure of those settings and not their values. MIT covers the code.
Frequently asked questions
What does Practical.CleanArchitecture actually contain?
A C# reference repository covering layered, hexagonal, onion, classic three-layer, modern four-layer and vertical-slice layouts, with monolith, modular monolith and microservice variants. Its README is mostly links to draw.io diagrams stored under docs/imgs, and it opens by warning that the samples are not always best practice.
How do you switch storage backends in Practical.CleanArchitecture?
A `Provider` key in the `Storage` section of appsettings.json selects one of three backends: Local with a `Path`, Azure with a connection string and container name, or Amazon with an access key, secret, bucket name and region endpoint. The default shown is Provider set to Local.
Which message brokers does Practical.CleanArchitecture support?
Four, selected by a `Provider` key under `Messaging`: RabbitMQ, Kafka, Azure Queue Storage and Azure Service Bus. RabbitMQ carries an ExchangeName and a RoutingKeys block, while the others use QueueNames, and Azure Queue Storage joins its queue names with hyphens where the other two join them with a low line.
Where can Practical.CleanArchitecture read its configuration from?
Two sources, each with an IsEnabled flag inside a ConfigurationSources block: a SQL Server table read with a query against ConfigurationEntries, and an Azure Key Vault identified by VaultName. The two can be enabled together in the same block.
Which deployment shapes does the Practical.CleanArchitecture README document?
Only the monolith. Every settings file it names is under src/Monolith, covering ClassifiedAds.WebMVC, ClassifiedAds.WebAPI and ClassifiedAds.Background, even though the repository description also advertises modular monolith and microservice variants.
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/phongnguyend-practical-cleanarchitecture)Star history chart for your README
[](https://hysenlabs.com/projects/phongnguyend-practical-cleanarchitecture)Was this useful?