Software Architecture with C# 12 and .NET 8: Build enterprise applications using microservices, DevOps, EF Core, and design patterns for Azure

El libro tiene una gran cantidad de información sobre las diferentes fases del ciclo de vida del Software, tanto de manera teórica como ejemplos prácticos. Su enfoque técnico es hacia Asp.Net Core, Azure y arquitectura de Microservicios. Aunque algunos temas no están orientados al detalle, la descripción de cada uno es muy bien realizado, de modo que, uno se da una idea de las diferentes implementaciones que existen en el mercado. Me parece muy válido por parte de los autores, abordar temas como Docker, Kubernetes, Blazor y MAUI (éste brevemente) porque esto nos da una mirada de todas las tecnologías que intervienen en los proyectos y lo que significa empezar una carrera como arquitectos. Así que si tenés dudas, empezá con la lectura de este libro y verás que muchas de ellas serán resueltas.

This book is a great resource for anyone looking to sharpen their software architecting skills or looking to learn more about these skills. This book will walk you through the process of architecting your applications using .NET and C#. If you aren't a .NET or C# developer you can still benefit from going through this book to learn the ins and out of what makes a good software architect. The examples and theory go hand in hand which will help you put the concepts together and have a great grasp of them to use in your own projects and career.

If you're involved in any aspect of software development, this book is an absolute essential addition to your library. I can't stress this enough: buy it now. Looking back, I wish I had encountered this gem earlier in my career. It brilliantly encapsulates numerous lessons I had to learn on the job, serving as a comprehensive resource that would have greatly accelerated my growth had I possessed its insights from the outset. The authors cover a vast array of topics, providing not only foundational knowledge but also invaluable insights into the intricacies of software development. Their expertise shines through, making this book an indispensable companion for anyone navigating the complexities of the field. While C# and .NET understandably receive ample attention within these pages, the book transcends mere language specifics. It equips readers with the skills and understanding necessary to thrive in enterprise-level environments, delving into essential technologies and ideologies that are practically mandatory for success. What truly sets this book apart is its accessibility. Despite addressing advanced concepts, it remains remarkably beginner-friendly, offering clarity where other resources might falter. The authors adeptly touch upon crucial subjects often overlooked by introductory texts, ensuring a well-rounded education for readers at any stage of their careers. Even seasoned engineers stand to benefit significantly from this tome. Personally, I found the discussions on Azure, Docker, Kubernetes, and microservices particularly enlightening, as they provided fresh perspectives on technologies that are less commonly encountered in my day-to-day work. In summary, this book is a game-changer. It deserves a prominent place in every engineer's collection, serving as both a comprehensive reference guide and a catalyst for professional growth. Trust me, you won't regret making this investment in yourself and your career.

Very few books exist, as far as I know, that cover the Software Engineering on the theo-practical level, and this is one of them. The book, in my view, scores better in the theory department, and very fairly in the practical, thus the four stars. I, overall, just like the practical books that teach you something new, but this is an important book for Software Architects and Senior Developers, as well as anybody who wants to "see the bigger picture" in a project. This is how this book has two parts: one on the general best practices, approaches, and industry knowledge, and the other on specific technologies related to the discussed in the first part. This makes logical sense to me, but dictates to read the book cover to cover, again in my prospective. The book will give you solid grounds to delivering a modern solution - from conducting CI/CD to hosting your microservices on Kubernetes, choosing a database and developing client side rendering on Blazor. Speaking of the microservies, strangely, three chapters are covering them which let me repeat it requires reading the entire book. Things to improve would be a better coverage of Blazor (frankly, it is a waste technology and luckily Packt released several great books covering the latest advancements in it recently), then another would be the chapter on SOA, in my opinion it is no longer popular. Lastly, one other smaller improvement is that AI and ML deserve dedicated chapters for being ubiquitous these days. I wish you an enjoyable reading!

I might alter this review because I've only gone thru the first 4 chapters, but feel that a kind of warning needs to be issued. Ya know the joke about winning a vacation, but 2/3rds of the time you're required to sit thru presentations on how to invest in timeshares? That's my impression of this book so far. They mention, "as a software architect," so many times, it might as well be a drinking game. Will this book eventually be worth more than a C# cookbook and 20 minute video on Domain Driven Design? I hope so, but if your focus is a large development project, where you're "main hat" is writing code, then I don't think you are the target audience for this book.

This book takes you by the hand through all phases of the development process. From the gathering of requirements to the installation on Azure containers. Always considering the design of the solution architecture. A good book if you are using this platoform.

This book prioritizes breadth over depth, but still manages to convey the majority of important information for any given architecture topic. I have been incredibly pleased by how concise, knowledgeable, and thorough the authors are. This book actually gives expert insight. Similar to how 'C# in depth' is less of a tutorial book and more of a deep dive, this book stays on my desk as a second reference when I don't feel like digging through stack overflow for the theory behind things. This has been very helpful for refactoring a legacy application into a modern minimal-api based .NET project leveraging microservices.

good one

Content is great and well explained, the editing/printing could be a bit better though, some images lack definition or focus and the text font used isn't the easiest to read, but the content is great and that's the most important.

I like to say this is the last piece in my .NET journey. I'm an experienced dev that already worked as TL using other technologies. I started learning .NET like 2 years and half from now. During those 2 years I read a lot of books in specific areas of the .NET platform (Unity, ASP.NET, EF Core, Blazor, etc) because I needed them for my job. This book is the last piece (and second one regarding architecture with .NET) of this journey. The book covers all the stuff you will need to design and build strong and reliable software starting from the foundation, the architecture. This is not a book for beginners, the authors assume you know the C# basics. But if you took a class of software engineering before most of the terms should sound familiar; at least in the few first chapters. The organization of the book couldn't be better. It starts from the basics of architecture, the functional and non-functional requirements; the latter term is something I haven't seen being used in a while hahaha. After that it shows how to manage them, you can tell how experienced the authors are at this point. After that everything should be easier to follow for you. The authors share their expertise in best practices showing some great examples on how to avoid messing up with your codebase. This will prepare you to move on to the next chapters that jumps back to the main topic, Architecture. The book will present the most used, in their experience, ways to architecture software. In my opinion is nice to not only have trending topics, but as well some of the patterns the industry followed the last 5-10 years. At that point you should be ready to apply all the new stuff presented in a very well-organized project. I personally appreciate the project is scoped to only 1 chapter. So, you don't get lost between learning new stuff and following the project at the same time. All these things are presented using mostly Microsoft technologies, of course haha. But the author also mentions alternatives and uses other well know technologies. I am actually excited to apply the things I learned in a personal project I was meant to start some time ago.

Questo è il quarto libro “packt” che acquisto e continuo a rimanere del parere che siano i migliori per quanto riguarda la manualistica tech. Anche questo libro è fatto molto bene, apprezzo molto la chiarezza espositiva dei contenuti e il fatto che, seppur gli argomenti siano di livello avanzato, le spiegazioni a corredo sono molto chiare e precise. Un ulteriore aspetto positivo è dato dal fatto che, molti concetti, decisioni, o pattern scelti sono spiegati con l’ausilio di esempi pratici dal mondo reale, non lasciando quindi la teoria campata in aria. Gli autori Gabriel Baptista e Francesco Abbruzzese sono nomi noti nel settore e non hanno bisogno di presentazioni, ragion per cui si capisce che le nozioni espresse nel libro sono frutto di esperienza sul campo con clienti reali. Il libro affronta diverse tematiche avanzate partendo da un livello di conoscenza medio/alto, per questo non è decisamente rivolto ai principianti di C#/.NET (per questo scopo consiglio altri libri, ad esempio io ho preso quelli di Mark J. Price, “C# 12 and .NET 8” e “Apps and Services with .NET 8”), ma a chi vuole diventare Software Architect oppure lo è già ma vuole aggiornarsi con le ultime tecnologie di tendenza. Gli argomenti trattati sono tanti e anche piuttosto complessi (tra i tanti: Design Pattern, DevOps, CI/CD, DDD, Microservices, EF Core, Kubernetes). Ovviamente con questo libro non si diventa esperti di ognuno: è chiaro che non basterebbe un’intera enciclopedia per trattarli tutti in profondità (giusto per citare un esempio, non vengono trattati tutti i design pattern ma “solo” quelli ritenuti indispensabili per poter efficacemente progettare architetture software mantenibili – comunque tanti). In ogni caso, se si vuole approfondire l’argomento, risulta molto utile la sezione “Further reading” presente alla fine di ogni capitolo. Unico neo, forse un po’ troppo discorsiva la parte sulla raccolta dei requisiti e delle specifiche; capisco però che per loro natura deve essere per forza di cose così. Penso che nel libro siano condensate tutte le conoscenze per essere in grado di progettare, sviluppare e distribuire un’applicazione di livello enterprise, con determinati requisiti di sicurezza e scalabilità. Molto utile anche il capitolo sul “Case Study”, dove si affronta la realizzazione di un esempio reale e concreto. In definitiva, personalmente ritengo questo libro decisamente ottimo per chi, come me, ambisce a diventare software architect o vuole conoscere o aggiornarsi sulle varie tecnologie relative alle architetture software.