Clean Architecture Fundamentals

Explore the single responsibility principle within SOLID, showing how a module should have one reason to change by separating cart calculations, discounts, totals, and purchase submission in an e-commerce example.

Apply the open-closed principle by structuring software with a business layer and a data access layer, making behavior extendable without modifying existing artifacts.

Explore the Liskov substitution principle, where superclass objects must be replaceable by subclasses without breaking the application, illustrated by the duck with batteries and the square versus rectangle case.

Present the interface segregation principle by showing defined responsibilities and dependencies on only what is necessary, using separate student, class, and parent repositories to save data.

Apply the dependency inversion principle by making high level modules depend on abstractions, not on low level details; use interfaces and dependency injection to wire concrete implementations.

discover clean architecture variants—onion, hexagon, and ports and adapters—centering entities and business rules, with layered UI and infrastructure and strict dependency rules.

Run a web api project with default settings, enable swagger, and use the weather forecast controller to try out and return sample forecasts.

Demonstrates creating an extension class to add swagger via extension methods on IServiceCollection, enabling endpoint explorer and swagger gen, and keeping program.cs lean while validating the setup.

Create a sort controller as a web api endpoint that accepts an int array via post and returns the same list after applying a bubble sort.

Explore the core layer in clean architecture, defining abstractions and interfaces, and applying dependency inversion and dependency injection to wire the sort service through program startup (ISortService).

Review the solid principles: single responsibility, open and closed, Liskov substitution. Align these with the C4 model diagrams: system context, container, component, and code, within a domain-centric clean architecture.

validate architecture through unit tests and dependency checks across presentation, infrastructure, application, and core layers, and automate violations in builds to prevent releases.