Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Software Architecture with C# 10 and .NET 6 – Third Edition

You're reading from   Software Architecture with C# 10 and .NET 6 – Third Edition Develop software solutions using microservices, DevOps, EF Core, and design patterns for Azure

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781803235257
Length 714 pages
Edition 3rd Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Francesco Abbruzzese Francesco Abbruzzese
Author Profile Icon Francesco Abbruzzese
Francesco Abbruzzese
Gabriel Baptista Gabriel Baptista
Author Profile Icon Gabriel Baptista
Gabriel Baptista
Arrow right icon
View More author details
Toc

Table of Contents (27) Chapters Close

Preface 1. Understanding the Importance of Software Architecture FREE CHAPTER 2. Non-Functional Requirements 3. Documenting Requirements with Azure DevOps 4. Deciding on the Best Cloud-Based Solution 5. Applying a Microservice Architecture to Your Enterprise Application 6. Azure Kubernetes Service 7. Interacting with Data in C# – Entity Framework Core 8. How to Choose Your Data Storage in the Cloud 9. Working with Azure Functions 10. Design Patterns and .NET 6 Implementation 11. Understanding the Different Domains in Software Solutions 12. Implementing Code Reusability in C# 10 13. Applying Service-Oriented Architectures with .NET 14. Implementing Microservices with .NET 15. Presenting ASP.NET Core MVC 16. Implementing Frontend Microservices with ASP.NET Core 17. Blazor WebAssembly 18. Native versus Web Clients 19. Artificial Intelligence and Machine Learning 20. Best Practices in Coding C# 10 21. Understanding DevOps Principles 22. Challenges of Applying CI & CD Scenarios 23. Testing Your Enterprise Application 24. Answers
25. Other Books You May Enjoy
26. Index

Choosing between SQL or NoSQL document-oriented databases

As a software architect, you may consider some aspects of SQL and NoSQL databases 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 document-oriented databases should be preferred when data has almost no predefined structure. They 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 if 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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime