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

How to choose your data storage in the cloud

In Chapter 12, Choosing Your Data Storage in the Cloud, we learned how to use NoSQL. Now we must decide whether NoSQL databases are adequate for our book use case WWTravelClub application. We need to store the following families of data:

Information about available destinations and packages: Relevant operations for these data are reads since packages and destinations do not change very often. However, they must be accessed as fast as possible from all over the world to ensure a pleasant user experience when users browse the available options. Therefore, a distributed relational database with geographically distributed replicas is possible but not necessary since packages can be stored inside their destinations in a cheaper NoSQL database.
Destination reviews: In this case, distributed write operations have a non-negligible impact. Moreover, most writes are additions since reviews are not usually updated. Additions benefit...