Clean Architecture for Beginners: A Practical Guide

Demonstrate separation of concern and software architectures using a cargo shipping app that searches trips, shows port routes, and flags delays when actual hours exceed standard by 10%.

Explore how a Windows Forms example shows the absence of separation of concerns by mixing data access, business logic, and UI in one form.

Apply a three-layer architecture to separate UI, business logic, and data access, using a service layer, repository layer, and domain layer to support a display view model.

Explore dependency injection and inversion of control to decouple service and repository layers by using abstractions and wiring dependencies with the Microsoft extensions dependency injection package.

Examine how a data-centric layered architecture creates a disconnect between business intent and code, highlighting maintenance challenges as the UI, service, repository, and domain dependencies flow one way.

Identify how data-centric layered architectures cause business logic to leak into the repository or UI, including stored procedures, and risks when switching technologies or data stores due to weak intent.

Analyze a data-centric, technology-driven architecture and apply separation of concerns by organizing modules around technologies, using a horizontally sliced, multi-layer layout with folders, controllers, and serializers.

Explore intent driven architecture through a car rental app, examining the screaming architecture’s vertical slices and the resulting complexity. Seek a middle ground that exposes business intent without overkill.

Explore the middle ground between technology-driven and intent-based architectures by proposing a structure that balances both technologies and intent.

Explore onion architecture, a type of clean, layered architecture that keeps core business and use cases independent from UI and database, with dependencies flowing inward.

Explore how the database can be implemented as a plugin that plugs into the use case layer through an abstraction, enabling plugin-based development within clean architecture and onion architecture.

Apply clean architecture to a cargo shipping app by centering the core business and use case layers in an onion, with inward dependencies and dependency injection for repository plugins.

Clean architecture clarifies intent by organizing use cases by screen or feature, and keeps business logic from leaking into the UI by isolating core logic in a dedicated middle tier.

Keep all business logic in the use cases and core layer, self-contained and framework independent, enabling use with Blazor, Angular, React, or Vue.js.

Implement the view ports use case in clean architecture, expose ports via a port repository, and wire it to the UI to filter trips by a selected port.

Implement the search by port use case in a clean architecture, inject the trip segment repository, and map results to trip segment view models.

Identify the common architecture mistake of coupling business logic to framework design patterns, such as Windows Forms and MVC controllers, and learn to move logic into plane classes.