architecture
Clean Architecture in .NET Articles, Tutorials & News
Clean Architecture in .NET articles, tutorials, and news from the DotNetNews archive.
265 articles Updated
Clean Architecture .NET is the focus of this topic page. Clean Architecture in .NET is a recurring focus for C# and .NET developers working in the Microsoft ecosystem. Intermediate and senior .NET developers use this hub to scan practical writing without treating every link as an endorsement.
Recurring subtopics in recent issues include Clean Architecture .NET, Clean Architecture C#, layered architecture .NET, and dependency inversion .NET. Those themes are drawn from titles and excerpts in the newest archive entries for this tag, not from a marketing outline.
Expect publisher tutorials, release notes, architecture write-ups, and field notes linked from DotNetNews issues. Start here is a short editorial shortlist for Clean Architecture in .NET; the archive list is chronological and larger. Secondary angles such as Clean Architecture .NET and Clean Architecture C# appear when the archive actually covered them. Nearby reading often overlaps with Domain-Driven Design in .NET and CQRS in .NET.
Start here
Editor picks for Clean Architecture
-
Building a Multi-Vertical Clean Architecture Platform for Azure Functions (.NET 10)
Medium Issue #504
Azure Functions plus clean architecture plus .NET 10 makes for a relevant architecture read, especially for growing API platforms.
-
SOLID on .NET: From Spaghetti Code to Clean Architecture (Practical Refactoring)
Medium Issue #503
I appreciate refactoring-focused SOLID content more than theory dumps, especially when it connects to clean architecture tradeoffs.
-
Multi-Tenant Saas Architecture
C# Corner Issue #497
Multi-tenant SaaS architecture is all trade-offs; I’d read this mainly for the tenant isolation and request pipeline decisions.
-
EF Core in Clean Architecture the Pragmatic Way
Dev Tips Issue #484
I like the pragmatic framing here; using DbContext directly can be perfectly reasonable when the boundaries stay clear.
-
Refactoring an ASP.NET Core API with clean architecture
Round The Code Issue #478
Clean architecture content can get vague; this one stays grounded in refactoring an API.
-
Clean Architecture in .NET: Benefits, Challenges, and Implementation Guide
C# Corner Issue #471
Clean Architecture fundamentals with practical .NET examples and real implementation challenges covered.
-
Implementing Clean Architecture in .NET 10 - Step-by-Step Guide
codewithmukesh Issue #471
CodeWithMukesh delivers another comprehensive guide, this time Clean Architecture with .NET 10 and Aspire.
-
Implementing Clean Architecture in .NET 10 - Step-by-Step Guide
codewithmukesh Issue #466
Beginner-friendly, but still useful as a current reference for structuring a .NET 10 application with EF Core and Aspire.
Archive
Page 1 of 11
Newest first
-
Vertical Slice vs Clean Architecture in .NET 10 - What I Use
codewithmukesh Issue #579
Vertical Slice vs Clean Architecture in .NET 10: real file counts, a decision matrix, and the pragmatic hybrid I recommend, with architecture tests.
-
Stop Adding Layers Just Because It’s “Clean Architecture”
Medium Issue #578
There is something that still annoys me in .NET projects.
-
Building a Secure JWT Authentication & Refresh Token System with Clean Architecture in ASP.NET Core
C# Corner Issue #578
Build JWT and refresh-token authentication in ASP.NET Core using Identity, token rotation, Clean Architecture, and a repository-based persistence layer.
-
EF Core in Clean Architecture the Pragmatic Way
Medium Issue #572
Clean Architecture is one of the most popular architectural styles in .NET today.Continue reading on CodeX »
-
Software Architecture in .NET C#: Shaping applications that survive change
Medium Issue #571
Every application has an architecture. The only question is whether someone chose it, or whether it simply happened, one urgent feature at…
-
Clean Architecture in ASP.NET Core: What Belongs in Each Layer, and Why?
Medium Issue #570
Understanding the responsibilities of each layer, the direction of dependencies, and the engineering decisions behind maintainable .NET…
-
Architecting Robust ASP.NET Core Applications with Clean and Onion Architecture
C# Corner - Sardar Mudassar Ali Khan Issue #564
-
Automating Validation in Clean Architecture: FluentValidation with MediatR Pipeline Behaviors
C# Corner - Sardar Mudassar Ali Khan Issue #563
-
Mastering CQRS and MediatR in Clean Architecture for ASP.NET Core
C# Corner - Sardar Mudassar Ali Khan Issue #562
-
Building Enterprise-Grade APIs: The Ultimate End-to-End Guide to Clean Architecture, CQRS, MediatR, FluentValidation, and Global Exception Handling in ASP.NET Core
C# Corner - Sardar Mudassar Ali Khan Issue #562
-
The “Captive Dependency” Trap: Understanding .NET DI Lifetimes
Medium - Satyam Pushkar Issue #554
In modern .NET applications, Dependency Injection (DI) is the backbone of clean, maintainable architecture. We rely on the built-in IoC…
-
C# DIY Compiler with DDD and Clean Architecture
Medium Issue #549
Compiler projects are often presented as pipelines of algorithms: lexing, parsing, analysis, and code generation. Once the project grows…
-
Clean Architecture in .NET: When It Helps and When It Becomes Overengineering
blog.stackademic.com Issue #544
Clean Architecture is one of those topics that almost every experienced .NET developer eventually runs into. At first, it feels like the… Continue reading on Stackademic »
-
How to Make AI Write High-Quality Code in .NET
Dev Tips Issue #539
AI writes .NET code fast, but it only follows the rules it cannot skip. Learn how to set up build guardrails, static analysis, and a Claude review skill that catches clean code issues on every change.
-
How to Choose Code Architecture in 2026
Dev Tips Issue #538
What code architecture uses fewer AI tokens? Advantages (pros) and disadvantages (cons) of N-Layered Architecture, Clean Architecture and Vertical Slice Architecture. How to combine Clean Architecture
-
Building Architecture Rules for AI-Generated Pull Requests in .NET
C# Corner Issue #532
Learn how to enforce architecture rules on AI-generated .NET pull requests using dependency checks, layering rules, forbidden references, and automated validation.
-
Abstractions via Interfaces: Decoupling External Services from Business Logic
Medium Issue #531
Abstraction is the bridge that allows your core application logic to interact with databases and external services without becoming…
-
We built a modular CMS and deliberately did not make the modules plugins
Medium Issue #531
BarakoCMS is a .NET headless CMS with thirteen optional modules: accounting, semantic search, feature flags, file storage, social sign-in…
-
Keep Your Application Layer Clean: FluentValidation and Mapster in .NET Clean Architecture
Medium Issue #530
How to stop your services from drowning in if/else validation and manual mapping code
-
I Built a Full-Stack Bug Tracker with .NET and React: Here’s What I Learned
Medium Issue #528
Clean Architecture on the backend, a hard line between server and client state on the frontend, and the small choices that mattered more…
-
Building Architecture Drift Detection into .NET Pull Requests
C# Corner Issue #527
Build automated architecture drift detection into .NET pull requests to enforce architectural rules, identify dependency violations, and prevent unintended design changes in CI.
-
Building Architecture Fitness Functions for AI-Generated .NET Code
C# Corner Issue #527
Build architecture fitness functions for AI-generated .NET code to automatically enforce architectural boundaries, dependency rules, layering constraints, design standards, and quality checks in CI pi...
-
Monolith vs Clean Architecture: Is Your .NET Project Actually Built to Grow?
Medium Issue #525
Why We Separate Layers in Projects: Monolith vs Clean Architecture
-
Preventing Architecture Drift with Executable Dependency Rules
C# Corner Issue #522
Prevent architecture drift with executable dependency rules. Turn architectural decisions into automated tests for C# applications using ArchUnitNET.
-
The Lazy Engineer’s Blueprint
Medium Issue #521
Why I stopped re-deciding the same twenty things on every .NET Web API, the four-move contract, and the map of the whole series.