You're reading from Software Architecture with C# 12 and .NET 8 Build enterprise applications using microservices, DevOps, EF Core, and design patterns for Azure

Product type Paperback

Published in Feb 2024

Publisher Packt

ISBN-13 9781805127659

Length 756 pages

Edition 4th 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 FREE CHAPTER

2. Non-Functional Requirements

3. Managing Requirements

4. Best Practices in Coding C# 12

5. Implementing Code Reusability in C# 12

6. Design Patterns and .NET 8 Implementation

7. Understanding the Different Domains in Software Solutions

8. Understanding DevOps Principles and CI/CD

9. Testing Your Enterprise Application

10. Deciding on the Best Cloud-Based Solution

11. Applying a Microservice Architecture to Your Enterprise Application

12. Choosing Your Data Storage in the Cloud

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

14. Implementing Microservices with .NET

15. Applying Service-Oriented Architectures with .NET

16. Working with Serverless – Azure Functions

17. Presenting ASP.NET Core

18. Implementing Frontend Microservices with ASP.NET Core

19. Client Frameworks: Blazor

20. Kubernetes

21. Case Study

22. Case Study Extension: Developing .NET Microservices for Kubernetes

23. Answers

24. Other Books You May Enjoy

25. Index

Understanding unit and integration tests

Testing is an essential part of software development since it verifies both that the software is bug-free and that it conforms to the agreed specification. Delaying application testing until immediately after most of the application’s functionalities have been implemented in their entirety must be avoided for the following reasons:

If a class or module has been incorrectly designed or implemented, it might have already influenced the way other modules were implemented. Therefore, at this point, fixing the problem might have a very high cost.
The possible combination of input that is needed to test all possible paths that execution can take grows exponentially with the number of modules or classes that are tested together. Thus, for instance, if the execution of a class method A can take three different paths, while the execution of another method B can take four paths, then testing A and B together would require 3 x...