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

Communication and data serialization

As explained in the Microservices design principles subsection of Chapter 5, Applying a Microservice Architecture to Your Enterprise Application, requests to a microservices-based application can’t cause long chains of recursive microservices calls. In fact, each call adds both a wait time and a communication time to the actual processing time, thus leading to unacceptable levels of overall response time, as shown in the figure below.

Figure 14.1: Tree of blocking RPC calls

Messages 1-6 are triggered by a request to the A microservice and are sent in sequence, so their processing times sum up to the response time. Moreover, once sent, message 1 from microservice A remains blocked till it receives the last message (6); that is, it remains blocked for the whole lifetime of the overall recursive communication process.

Microservice B remains blocked twice, the first time during the 2-3 communication and then during the 4-5...