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

Choosing between structured or NoSQL storage

As a software architect, you may consider some aspects of structured and NoSQL storage to decide the best storage option for you. In many cases, both will be needed. The key point here will surely be how organized your data is and how big the database will become.

In the previous section, we stated that NoSQL databases should be preferred when data has almost no predefined structure. NoSQL databases not only keep variable attributes close to their owners, but they also keep some related objects close since they allow related objects to be nested inside properties and collections.

Unstructured data can be represented in relational databases since variable properties of a tuple, t, can be placed in a connected table containing the property name, property value, and the external key of t. However, the problem in this scenario is performance. In fact, property values that belong to a single object would be spread all over the available...