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

Transitioning to microservices

You don’t have to transition your monolith to microservices; deploying a monolith is fine if it fits your needs. However, if ever you need to, you could shield your aggregator with a gateway or a reverse proxy so you can extract modules into their own microservices and reroute the requests without impacting the clients. This would also allow you to gradually transfer the traffic to the new service while keeping the monolith intact in case of an unexpected failure.

In a Modular Monolith, the aggregator registers most dependencies, so when migrating, you must also migrate this shared setup. One way to not duplicate code would be to create and reference a shared assembly containing those registrations. This makes it easier to manage the dependencies and shared configurations, but it is also coupling between the microservices and the aggregator. Leveraging the code of this shared assembly is even easier when the microservices are part of the same...