Transcription of Clean Architecture with ASP.NET Core
{{id}} {{{paragraph}}}
Clean Architecturewith CoreS T E V E S M I T HA R D A L I S .C O M | @A R D A L I S| S T E V E @ D E V I Q .C O MD E V I Q .C O MLearn More After Today1) Pluralsight N-Tier Apps with C# Domain-Driven Design ) DevIQ Core Quick ) Microsoft FREE eBook/SampleApp ) Contact me for mentoring/training for your company/teamQuestionsHOPEFULLY YOU LL KNOW THE ANSWERS WHEN WE RE DONEWhy do we separateapplications into multiple projects?What are some principleswe can apply when organizingour software modules?How does the organizationof our application s solutionimpact coupling?What problemsresult from certain common approaches?How does Clean Architecture address these problems?Oh yeah, and isn t Core pretty cool? :)PrinciplesA B I T O F G U I D A N C ESeparation of ConcernsAvoid mixing different code responsibilities in the same (method | class | project)The Big Three Data Access Business Rules and Domain Model User InterfaceSingle ResponsibilityWorks in tandem with Separation of ConcernsClasses should focus on a single responsibility a single reason to Don t Repeat Refactor repetitive codeinto functions Group functions into cohesive classes Group classes into folders and namespacesby Responsibility Level of abstraction Etc.
Work with an application service. 1) Pass ApiModel types to service 2) Service internally works with repositories and domain model types. 3) Service returns a web model type Better for more complex operations Application Service is responsible for …
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}