Software Architecture with C++: Design modern systems using effective architecture concepts, design patterns, and techniques with C++20

If you purchase this book hoping for a 'how to' guide with lots of c++ code, you may be disappointed. There is actually not much code examples in the book.Therefore my headline: it's about the architecture. This book summarises the best known patterns, idioms, and practices in system design. The first chapters give a thorough revision of basic principles like SOLID, coupling, cohesion, monolith or service based architecture, etc. Many third party products and external c++ libraries are mentioned to design modern c++ systems in line with current practices. If you fell behind with system design and wish to catch up, or are new to it and need a great overview of the field, this book will be of great value.The authors cover a lot of material. The book does not go in depth on each of the many topics. The authors make the reader aware that a design principle, product, library or technique exists, and provide links to more information in a further reading section at the end of each chapter.Highly recommended reading as a reference guide or introduction to c++ system design.

The book is written as a collection of topics, which are often quickly just announced, reported and never really described.An example is the security chapter reporting a list of vulnerabilities (list of the names).Another example is the unit test chapter listing minimal and insufficient examples for some libraries in c++.When you have to search on internet what the authors missed to clearly say, then the book lost ist uselness.

Well written, compact review of modern software infrastructure, tools and to the point. I like that the writing style, practical examples that are easy to understand. My only critique of the book is about the index, it is not very detailed and make it difficulty to use this book as a reference.

This book covers most of the usual Software Architecture topics, according to my experience. From design patterns to infrastructure development. It is a good reference to have on your shelf for introducing oneself to this world.Good work authors. If I had to criticize one thing, that would be the quality of the book covers - but that is a Packt problem. Surprisingly, this contrasts with the quality of the paper, which is relatively good.

The book was written so erratically that I put it aside after 50 pages. In terms of content, an attempt is made to convey a lot of opinion and poorly founded knowledge. Too bad.The authors may be good developers, but writing books is a different story.