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

The repository and Unit of Work patterns

The repository pattern is an entity-centric approach to the definition of the domain layer interfaces: each aggregate has its own repository interface that defines how to retrieve and save it, and that defines all queries that involve entities in the aggregate. The data layer implementation of each repository interface is called a repository.

With the repository pattern, each operation has an easy-to-find place where it must be defined: the interface of the aggregate the operation works on, or, in case of a query, the aggregate that contains the root entity of the query.

While it is preferable for transactions to be confined within the boundary of a single aggregate, design, sometimes application layer transactions might span several aggregates and, accordingly, might use several different repository interfaces. The Unit of Work pattern is a solution that maintains the independence of the domain layer from the underlying data layer...

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 €18.99/month. Cancel anytime