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

What are software domains?

As we discussed in Chapter 2, Non-Functional Requirements, and Chapter 3, Documenting Requirements with Azure DevOps, the transfer of knowledge from domain experts to the development team plays a fundamental role in software design. Developers try to communicate with experts and describe their solutions in a language that domain experts and stakeholders can understand. However, often, the same word has a different meaning in various parts of an organization, and what appear to be the same conceptual entities have completely different shapes in different contexts.

For instance, in our WWTravelClub use case, the order-payment and packages-handling subsystems use completely different models for customers. Order-payment characterizes a customer by their payment methods and currency, bank accounts, and credit cards, while packages-handling is more concerned with the locations and packages that have been visited and/or purchased in the past, the user&apos...