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

Summary

This chapter covered how you can create an Azure DevOps or GitHub account for a software development project and how to start managing your projects with Azure DevOps or GitHub projects.

It also gave a short review of all of Azure DevOps’ functionalities, explaining how to access them through the Azure DevOps main menu.

To finish, it presented the GitHub project view options to plan and manage a project.

The chapter also described in more detail how to manage system requirements and how to organize the work necessary with various kinds of work items or issues, along with how to plan and organize sprints that will deliver epic solutions with many features.

The decision of whether to use Azure DevOps or GitHub in a project will vary according to the expertise of the team and the objective of the project itself. If you are designing an open-source solution, GitHub will definitely be a better option. On the other hand, if you are designing an enterprise...