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

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781803235257

Length 714 pages

Edition 3rd Edition

Languages

Tools

.NET

Concepts

Design Patterns

Authors (2):

Francesco Abbruzzese

Gabriel Baptista

View More author details

Table of Contents (27) Chapters

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

How does .NET 6 deal with SOA?

WCF technology has not been ported to .NET 5+ and there are no plans to perform a complete port of it. Part of the source code was donated, and an open-source project started out of it. You can find information about this project at https://github.com/CoreWCF/CoreWCF. Instead, Microsoft is investing in gRPC, Google’s open-source technology. Besides, .NET 6 has excellent support for REST services through ASP.NET Core.

The main reasons behind the decision to abandon WCF are as follows:

As we have already discussed, SOAP technology has been overtaken by REST technology in most application areas.
WCF technology is strictly tied to Windows, so it would be very expensive to reimplement all its features from scratch in .NET 5+. Since support for full .NET will continue, users that need WCF can still rely on it.
As a general strategy, with .NET 5+, Microsoft prefers investing in open-source technologies that can be shared with...