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

Managing system requirements in Azure DevOps

Azure DevOps enables you to document system requirements using work items. Work items are stored in your project as chunks of information that can be assigned to a person. They are classified into various types and may contain a measure of the development effort required, a status, and the development stage (iteration) they belong to.

DevOps is usually combined with agile methodologies, so Azure DevOps uses iterations, and the whole development process is organized as a set of sprints. The work items available depend on the work item process you select while creating the Azure DevOps project. The following subsections contain a description of the most common work item types that appear when an Agile or Scrum work item process is selected (the default is Agile).

Epic work items

Imagine you are developing a system comprising various subsystems. You are probably not going to conclude the whole system in a single iteration. Therefore...