You're reading from Software Architecture with C# 10 and .NET 6 – Third Edition Develop software solutions using microservices, DevOps, EF Core, and design patterns for Azure

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781803235257

Length 714 pages

Edition 3rd Edition

Languages

Tools

.NET

Concepts

Design Patterns

Authors (2):

Francesco Abbruzzese

Gabriel Baptista

View More author details

Table of Contents (27) Chapters

Preface

1. Understanding the Importance of Software Architecture FREE CHAPTER

2. Non-Functional Requirements

3. Documenting Requirements with Azure DevOps

4. Deciding on the Best Cloud-Based Solution

5. Applying a Microservice Architecture to Your Enterprise Application

6. Azure Kubernetes Service

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

8. How to Choose Your Data Storage in the Cloud

9. Working with Azure Functions

10. Design Patterns and .NET 6 Implementation

11. Understanding the Different Domains in Software Solutions

12. Implementing Code Reusability in C# 10

13. Applying Service-Oriented Architectures with .NET

14. Implementing Microservices with .NET

15. Presenting ASP.NET Core MVC

16. Implementing Frontend Microservices with ASP.NET Core

17. Blazor WebAssembly

18. Native versus Web Clients

19. Artificial Intelligence and Machine Learning

20. Best Practices in Coding C# 10

21. Understanding DevOps Principles

22. Challenges of Applying CI & CD Scenarios

23. Testing Your Enterprise Application

24. Answers

25. Other Books You May Enjoy

26. Index

Implementing worker microservices with ASP.NET core

In this section, we will show you how to implement a microservice that receives communications through gRPC and an internal queue based on a database table. The example is a part of the WWTravelClub book use case. The first subsection briefly describes the microservice specifications and the overall architecture.

The problem and the architecture

Our example microservice is required to compute the daily sums of all purchases. According to the data-driven approach, we suppose that all daily sums are pre-computed by receiving messages that are sent as soon as a new purchase is finalized. The purpose of the microservice is to maintain a database of all purchases and of all daily sums that can be queried by an administrative user. We will implement just the functionalities needed to fill the two database tables.

The implementation described in this section is based on an ASP.NET Core application that hosts a gRPC service....