Book Image

An Atypical ASP.NET Core 5 Design Patterns Guide

By : Carl-Hugo Marcotte
Book Image

An Atypical ASP.NET Core 5 Design Patterns Guide

By: Carl-Hugo Marcotte

Overview of this book

Design patterns are a set of solutions to many of the common problems occurring in software development. Knowledge of these design patterns helps developers and professionals to craft software solutions of any scale. ASP.NET Core 5 Design Patterns starts by exploring basic design patterns, architectural principles, dependency injection, and other ASP.NET Core mechanisms. You’ll explore the component scale as you discover patterns oriented toward small chunks of the software, and then move to application-scale patterns and techniques to understand higher-level patterns and how to structure the application as a whole. The book covers a range of significant GoF (Gangs of Four) design patterns such as strategy, singleton, decorator, facade, and composite. The chapters are organized based on scale and topics, allowing you to start small and build on a strong base, the same way that you would develop a program. With the help of use cases, the book will show you how to combine design patterns to display alternate usage and help you feel comfortable working with a variety of design patterns. Finally, you’ll advance to the client side to connect the dots and make ASP.NET Core a viable full-stack alternative. By the end of the book, you’ll be able to mix and match design patterns and have learned how to think about architecture and how it works.
Table of Contents (27 chapters)
1
Section 1: Principles and Methodologies
5
Section 2: Designing for ASP.NET Core
11
Section 3: Designing at Component Scale
15
Section 4: Designing at Application Scale
21
Section 5: Designing the Client Side
25
Acronyms Lexicon

Implementing the CQRS pattern

CQRS stands for Command Query Responsibility Segregation. We can apply CQRS in two ways:

  • Dividing requests into commands and queries.
  • Applying the CQRS concept to a higher level, leading to a distributed system.

In this chapter, we stick with the first one, but we will tackle the second definition in Chapter 16, Introduction to Microservices Architecture.

Goal

The goal is to divide all requests into two categories: commands and queries.

A command mutates the state of an application. For example, creating, updating, and deleting an entity are commands. Commands do not return a value.

On the other hand, a query reads the state of the application but never changes it. For example, reading an order, reading your order history, and retrieving your user profile are all queries.

By performing this division, we create a clear separation of concerns between mutator and accessor requests.

Design

There is no definite design...