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

Before you begin: Join our book community on Discord

Give your feedback straight to the author himself and chat to other early readers on our Discord server (find the "architecting-aspnet-core-apps-3e" channel under EARLY ACCESS SUBSCRIPTION).

https://packt.link/EarlyAccess

Qr code Description automatically generated

This chapter delves into the heart of web application communication–REST APIs. In today's connected digital world, effective communication between different applications is paramount, and RESTful APIs play a pivotal role in facilitating this interaction.We start by exploring the basic fabric of the web: the HTTP protocol. We touch on the core HTTP methods such as GET, POST, PUT, and DELETE to see how they carry out CRUD (Create, Read, Update, Delete) operations in a RESTful context. We then turn our attention to HTTP status codes–the system's way of informing clients about the status of their requests–and HTTP headers.Since APIs evolve and managing these changes without disrupting...