Creating a modular, testable and maintainable application in .NET Core requires a solid foundation. Setting up an application architecture requires foresight and much consideration as early decisions will impact how easily the application is extended and maintained.
In the long run though, applications need to be maintained and in this case, extended. Between its design and the way the code was written, neither is really possible and so the application needs to be redesigned and future proofed.
Why SOLID Architecture?
When we talk about SOLID architecture, we are referring to isn’t a straightforward task. Decisions made early in the process can have a large impact later on, and maintainability and testability play an important role. Adopting these practices can also contribute to avoiding code smells, refactoring code, and facilitate more efficient agile development.
SOLID stands for:
S – Single–Responsibility Principle
O – Open–closed Principle
L – Liskov Substitution Principle
I – Interface Segregation Principle
D – Dependency Inversion Principle
In this course, you explore foundational architectural principles which help with the creation of maintainable code. You will discover how to set up a real–world application architecture with ASP.NET Core. Then, you’ll learn how to plug in different, common blocks such as email, authentication and have a foundation to plug–in other third–party services as needed.
Specification: ASP.NET Core – SOLID and Clean Architecture (.NET 5 and Up)