You're reading from Software Architecture with C# 12 and .NET 8 Build enterprise applications using microservices, DevOps, EF Core, and design patterns for Azure

Product type Paperback

Published in Feb 2024

Publisher Packt

ISBN-13 9781805127659

Length 756 pages

Edition 4th Edition

Languages

Tools

.NET

Concepts

Design Patterns

Authors (2):

Gabriel Baptista

Francesco Abbruzzese

View More author details

Table of Contents (26) Chapters

Preface

1. Understanding the Importance of Software Architecture FREE CHAPTER

2. Non-Functional Requirements

3. Managing Requirements

4. Best Practices in Coding C# 12

5. Implementing Code Reusability in C# 12

6. Design Patterns and .NET 8 Implementation

7. Understanding the Different Domains in Software Solutions

8. Understanding DevOps Principles and CI/CD

9. Testing Your Enterprise Application

10. Deciding on the Best Cloud-Based Solution

11. Applying a Microservice Architecture to Your Enterprise Application

12. Choosing Your Data Storage in the Cloud

13. Interacting with Data in C# – Entity Framework Core

14. Implementing Microservices with .NET

15. Applying Service-Oriented Architectures with .NET

16. Working with Serverless – Azure Functions

17. Presenting ASP.NET Core

18. Implementing Frontend Microservices with ASP.NET Core

19. Client Frameworks: Blazor

20. Kubernetes

21. Case Study

22. Case Study Extension: Developing .NET Microservices for Kubernetes

23. Answers

24. Other Books You May Enjoy

25. Index

Defining the application architecture

The application will be implemented with the Domain-Driven Design (DDD) approach and associated patterns described in Chapter 7, Understanding the Different Domains in Software Solutions, and Chapter 13, Interacting with Data in C# – Entity Framework Core, so having a good understanding of the content covered in those chapters is a fundamental prerequisite to reading this chapter.

The application is organized based on a DDD approach and uses SOLID principles to map your domain sections. That is, the application is organized into three layers, each implemented as a different project:

There’s a domain layer, which contains the repository’s implementation and the classes describing database entities. It is a .NET library project. However, since it needs some interfaces, like IServiceCollection, which are defined in Microsoft.NET.Sdk.web, and since the DBContext layer must inherit from the identity framework in...