You're reading from Architecting ASP.NET Core Applications An atypical design patterns guide for .NET 8, C# 12, and beyond

Product type Paperback

Published in Mar 2024

Publisher Packt

ISBN-13 9781805123385

Length 806 pages

Edition 3rd Edition

Languages

Tools

.NET

Concepts

Design Patterns

Author (1):

Carl-Hugo Marcotte

View More author details

Table of Contents (27) Chapters

Preface

1. Section 1: Principles and Methodologies FREE CHAPTER

2. Introduction

3. Automated Testing

4. Architectural Principles

5. REST APIs

6. Section 2: Designing with ASP.NET Core

7. Minimal APIs

8. Model-View-Controller

9. Strategy, Abstract Factory, and Singleton Design Patterns

10. Dependency Injection

11. Application Configuration and the Options Pattern

12. Logging Patterns

13. Section 3: Component Patterns

14. Structural Patterns

15. Behavioral Patterns

16. Operation Result Pattern

17. Section 4: Application Patterns

Anti-pattern – Big Ball of Mud

18. Layering and Clean Architecture

19. Object Mappers

20. Mediator and CQS Patterns

21. Getting Started with Vertical Slice Architecture

22. Request-EndPoint-Response (REPR)

23. Introduction to Microservices Architecture

24. Modular Monolith

25. Other Books You May Enjoy

26. Index

Using Minimal APIs with Data Transfer Objects

This section explores leveraging the Data Transfer Object (DTO) pattern with Minimal APIs.

This section is the same as we explore in Chapter 6, Model-View-Controller, but in the context of Minimal APIs. Moreover, the two code projects are part of the same Visual Studio solution for convenience, allowing you to compare the two implementations.

Goal

As a reminder, DTOs aim to control the inputs and outputs of an endpoint by decoupling the API contract from the application’s inner workings. DTOs empower us to define our APIs without thinking about the underlying data structures, leaving us to craft our REST APIs how we want.

We discuss REST APIs and DTOs in more depth in Chapter 4, REST APIs.

Other possible objectives are to save bandwidth by limiting the amount of information the API transmits, flattening the data structure, or adding API features that cross multiple entities.