Software Architecture with C# 10 and .NET 6: Develop software solutions using microservices, DevOps, EF Core, and design patterns for Azure, 3rd Edition

Very complete book on building and deploying an enterprise solutions in the Cloud. Covering all of the modern tools from Microsoft including Azure Functions, Kerbernetes service. Asp.Net Core and Blazor. Also covered are design patterns and dependency injection along with Domain Driven Design and Service Oriented Architecture. Its unusual to find books to cover this range of topics.

I have just recently started this book, it has lots of good content, and presents material in a logical way. The author takes the reader through each topic and provides practical real-world examples as you go. If you already have some basic knowledge of programming, I recommend this book. As it is for those who wish to improve their knowledge of C#. I am looking forward to finishing this book and I can already say it's a great resource for developers.

Most of the content is very surface level and doesn’t go into any depth.

This book takes the reader from a history of the various methodologies (something that was for me at least an interesting blast from the past) right through to design patterns and how they are implemented within the azure and .net ecosystems.It shows practical examples of how to do implement some of the most relevant software patterns as well as covering a beginner’s guide to Kubernetes/Docker, Serverless Functions, and various other Azure technologies such as AI. Detailed chapters on Entity Framework, data storage approach and even MVC/Blazor.The book covers a broad spectrum with the basics of Scrum and Kanban plus creating requirements and even Domain Driven Development. There are chapters on common coding errors such as string concatenation and how to do multi-threading which should be part of the code review, quality process that you as a technical architect help to define.The book was clearly laid out and highly readable even though it is technical.There are several things I would like to see in future editions of this book;At times, this book seems to almost cover too much ground. As a technical architect, there many areas where a broad knowledge of a subject is sufficient, and more attention could be given to the decision-making process as well as how to instil quality and set up the processes rather than in-depth code examples of technologies such as Blazor & MVC. Whilst these are interesting, they are not necessarily relevant to many organisations where React or Angular are more common SPA choices – showing that those also fit nicely into the Azure DevOps pipeline might have been more helpful.Testing is an incredibly important part of any professional developer software toolkit. There is a good whole chapter devoted to it at the back of the book (chapter 22) but it is barely mentioned throughout the rest of the book. Given the change to “shift left” over the last few years with better available DevOps pipelines and improved ubiquity of tools, this is something that should be considered with every line of code that is written. Testing should cover everywhere there is business logic including the database (where we can use tSQLt). I rarely see examples or considerations of how to test things within the code samples and would like to see it more prominently talked about.In the non-functional requirements it would be nice to see more anti-patterns talked about. One of which is the spaghetti hell of microservices all talking to each other because the architect has taken a more purist approach to services. The use of out of process calls are something that should be warned and considered like denormalization in SQL. This area also feeds into the joys of trying to create a transaction with microservices and how it works in an environment like Docker. Chapter 5 does talk about this structuring with paragraphs on “Loose coupling” and “No chained requests/responses” but the warning could be a little more clearly expressed.I would also like to see much more attention given to accessibility. If we design our systems to be accessible to everyone, we usually find that the side effect is that they are even easier to use by other users and the careful consideration of this also lends itself to easier integration testing and automation.Overall, I really like this book but there are a few areas as outlined above which might make it a little more focussed on the technical architect role.For full disclosure, I was given this book to review though I have tried to be as even handed as possible in my reviewJon Baggaley, Enterprise Architect

It is clear and concise and easy to follow

It's a good architecture book for solution development using .NET 6 and C# 10 for Microsoft Azure. It's a good book for experienced .NET and C# developers. Beginners must look at other books to learn Azure, C# and .NET.

Gli argomenti trattati sono tanti, una carrellata di argomenti senza mai entrare nel dettaglio. Solo alcuni capitolo sono apprezzabili.

Some chapters are perfect, but others go into the weeds on features. I would have expected an architecture book to stay on a higher, composition level.It also relies heavily on extraneous code samples. Those are ok for exercises but for the main concepts, I'd rather keep the experience in the book.I wish the rest of the book was more like Chapter 18! ...still working through Chapter 21, but it seems that chapters 18 on are more in line with what i expected from this book.