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.

Imagine spending thousands of dollars to attend some of the best world-class conferences. In addition to the cost of the conference, you will also incur travel costs, hotels, meals, parking, and the costs of the time spent being away from your fulltime job. While attending such conferences – you have the opportunity to sit in on sessions – presented by leading practitioners – but you will be challenged to decide which sessions to select – and you will inevitably have to miss out on some when choices must be made. Embodied in this book are some of the most important lessons that you might glean from attending several such conferences. The additional value of this book – is that it is concisely written – and in the latter chapters, provides a specialized focus through the lens of Software Architecture with C++. However, many of the lessons conveyed in its pages are applicable, regardless of your language choice. By learning C++ you will become a better programmer. Period. You will have a deeper understanding of the underlying design and performance considerations of all programming languages – and you will have added a powerful tool to your toolbox.This book is the equivalent of a Master Class in Software Architecture with C++

This provides thorough overview of and practical guidance for all aspects of building a modern distributed system for the intermediate to advanced C++ programmer.Building a modern distributed system is not just about designing the system; it is also about ensuring a accurate, reliable, and complete implementation of that system.This book focuses on all aspects of the design and implementation considerations to build a successful distributed system. It begins with a presentation of a variety of design approaches, such as stateful and stateless services, monolithic services versus microservices, layered architectures and module-bases architectures. Guidance on gathering and documenting requirements is covered. Many aspects of implementing the system in C++ are illuminated. Most significantly, the oft-overlooked concepts of testability, performance, scalability, and security. I was particularly pleased to see a practical discussion of code review during system development.The last chapters of the book takes a deeper dive on various architectures such as microservices, containers, web services, and cloud-native services. For each architecture, it provides useful tools and practical approaches for implementation and deployment.For any programmer who is individually or on a team responsible for developing, deploying,and/or maintaining a distributed system, this book is an indispensable guide to success.

Software Architecture is language agnostic. That is true when you want to teach or discuss high level concepts, or when you design a high level architecture; but when you face a real project, you need, in some way, to 'instantiate' those concepts, in order to do so you need real tools; going in that direction, it is great to have at hand a book that put together high level concepts with concrete and real tools that you can actually use to build your solution.   This book starts with the fundamental ideas and concepts of software architecture, and then it puts it down to earth with real examples and tools, this is extremely helpful in particular for those that are facing project's challenges and don't have experienced engineers on their team.    It is worth mentioning that the book is quite up to date covering topics like cloud, containers, microservices, c++20 concepts, etc. For sure there could be space for additions for future editions where more examples can be created or new topics can be covered putting in practice some architectural tools and libraries available on the STL or Boost Libraries for instance.    Great book overall.

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.