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

WWTravelClub – DOs and DON'Ts in writing code

As a software architect, you must define a code standard that matches the needs of the company you are working for.

In the sample project of this book (check out more about the WWTravelClub project in Chapter 1, Understanding the Importance of Software Architecture), this is no different. The way we decided to present the standard for it is by describing a list of DOs and DON'Ts that we followed while writing the samples we produced. It is worth mentioning that the list is a good way to start your standard and, as a software architect, you should discuss this list with the developers you have in the team so that you can evolve it in a practical and good manner.

In addition, these statements are designed to clarify the communication between team members and improve the performance and maintenance of the software you are developing: