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

Advanced Kubernetes concepts

In this section, we will discuss other important Kubernetes features, including how to assign permanent storage to StatefulSets, how to store secrets such as passwords, connection strings, or certificates, how a container can inform Kubernetes about its health state, and how to handle complex Kubernetes packages with Helm. All subjects are organized in dedicated subsections. We will start with the problem of permanent storage.

Requiring permanent storage

Since pods are moved among nodes, they can't rely on the permanent storage offered by the current node where they are running. This leaves us with two options:

Using external databases: With the help of databases, ReplicaSets can also store information. However, if we need a better performance in terms of write/update operations, we should use distributed sharded databases based on non-SQL engines such as Cosmos DB or MongoDB (see Chapter 9, How to Choose Your Data Storage...