You're reading from An Atypical ASP.NET Core 6 Design Patterns Guide A SOLID adventure into architectural principles and design patterns using .NET 6 and C# 10

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781803249841

Length 678 pages

Edition 2nd Edition

Languages

Tools

.NET

Concepts

Design Patterns

Author (1):

Carl-Hugo Marcotte

View More author details

Table of Contents (31) Chapters

Preface

1. Section 1: Principles and Methodologies

2. Introduction FREE CHAPTER

3. Automated Testing

4. Architectural Principles

5. Section 2: Designing for ASP.NET Core

6. The MVC Pattern Using Razor

7. The MVC Pattern for Web APIs

8. Understanding the Strategy, Abstract Factory, and Singleton Design Patterns

9. Deep Dive into Dependency Injection

10. Options and Logging Patterns

11. Section 3: Designing at Component Scale

12. Structural Patterns

13. Behavioral Patterns

14. Understanding the Operation Result Design Pattern

15. Section 4: Designing at Application Scale

16. Understanding Layering

17. Getting Started with Object Mappers

18. Mediator and CQRS Design Patterns

19. Getting Started with Vertical Slice Architecture

20. Introduction to Microservices Architecture

21. Section 5: Designing the Client Side

22. ASP.NET Core User Interfaces

23. A Brief Look into Blazor

24. Assessment Answers

25. Acronyms Lexicon

26. Other Books You May Enjoy

27. Index

Appendices

1. Appendix A

2. Appendix B

Introducing layering

Now that we’ve explored a few design patterns and played with ASP.NET Core a little, it is time to jump into layering. In most computer systems, there are layers. Why? Because it is an efficient way to partition and organize units of logic together. We could conceptually represent layers as horizontal chunks of software, each encapsulating a concern.

Classic layering model

Let’s start by examining a classic three-layer application design:

Figure 12.1: A classic three-layer application design

The presentation layer represents any user interface that a user can interact with to reach the domain. In our case, it could be an ASP.NET Core web application. However, anything from WPF to WinForms to Android could be a valid non-web presentation layer alternative.

The domain layer represents the core logic driven by the business rules; this is the solution to the application’s problem. The domain layer is also called the business...