You're reading from Software Architecture with C# 9 and .NET 5 Architecting software solutions using microservices, DevOps, and design patterns for Azure

Product type Paperback

Published in Dec 2020

Publisher Packt

ISBN-13 9781800566040

Length 700 pages

Edition 2nd 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

2. Non-Functional Requirements FREE CHAPTER

3. Documenting Requirements with Azure DevOps

4. Deciding the Best Cloud-Based Solution

5. Applying a Microservice Architecture to Your Enterprise Application

6. Azure Service Fabric

7. Azure Kubernetes Service

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

9. How to Choose Your Data Storage in the Cloud

10. Working with Azure Functions

11. Design Patterns and .NET 5 Implementation

12. Understanding the Different Domains in Software Solutions

13. Implementing Code Reusability in C# 9

14. Applying Service-Oriented Architectures with .NET Core

15. Presenting ASP.NET Core MVC

16. Blazor WebAssembly

17. Best Practices in Coding C# 9

18. Testing Your Code with Unit Test Cases and TDD

19. Using Tools to Write Better Code

20. Understanding DevOps Principles

21. Challenges of Applying CI Scenarios

22. Automation for Functional Tests

23. Answers

24. Another Book You May Enjoy

25. Index

When do microservices help?

The answer to this question requires us to understand the roles microservices play in modern software architectures. We will look at this in the following two subsections:

Layered architectures and microservices
When is it worth considering microservice architectures?

Let's start with a detailed look at layered architectures and microservices.

Layered architectures and microservices

Enterprise systems are usually organized in logical independent layers. The first layer is the one that interacts with the user and is called the presentation layer, while the last layer takes care of storing/retrieving data and is called the data layer. Requests originate in the presentation layer and pass through all the layers until they reach the data layer, and then come back, traversing all the layers in reverse until they reach the presentation layer, which takes care of presenting the results to the user/client. Layers can&apos...