Become an Awesome Software Architect: Book 1: Foundation 2019

Some 70% of all software development projects fail (depending on the definition of failure), and this number seems to stay the same for the last fifty years. The complexity of projects grows; new tools, languages, databases, ideas come up; but the projects still take longer than planned, over budget, and stressful for programmers and managers involved. Numerous books are available to address this issue, along with training courses, but they are either theoretical, or limited in scope to a particular language, tool or methodology.This book is a great attempt to address the problems of software development in a comprehensive fashion. The author does not promote any particular tool, giving instead an unbiased overview of what is available for programmers and in what situations what should be used. The book is relatively easy to read, though in some cases I had to check acronyms and definitions. The code samples are short and to the point; they are easy to follow no matter what programming language is your favorite. Quite a few important subjects are not addressed, so judging by "Book 1 - Foundation" on the title page, other books will follow. Looking forward...

Very good book, the topics are explained in a simple and concrete way so it's very simple to read. He don't stop much on giving detailed and boring definitions but mention just enought ir order to make a proper research later (if necessary). One of the key points of this book is that after you read It you will be able to put in practice most of the topics.One thing I would like to read on next edition is about error/exception handling and propagation through integrated systems/platforms.

A fun and informative read, more of an in depth overview than a deep technical manual, just what I was looking for actually. Author uses Typescript to explain his understandings and it works really well. All in all a great work on Software architecture...

I feel the book might be a good read for junior engineers who haven't thought much about how an architect makes decisions. However, it definitely lacks a systematic approach and the in-depth thinking needed to be proper for the title.

The book assumes that to really, actually create a good programming product, you need not only good architecture, but also the author on the project.The book implicitly explains and makes it obvious that there are much better ways of creating software much faster, much cheaper, and much better at the same time. However, to find these ways and to actually implement them you need some 20+ years of experience. Or spend 20-25 years researching the topic(s), unless you retain the author.Don't take me wrong, the pitch is implicit. It has very little to do with the "infomercials" out there. It's just price of the book barely covers typing the book. So, how much expertise you could put in without the price becoming unreasonable? Right, very little.

This guide is way beyond traditional books on software architecture.It provides holistic view on what’s needed to deliver, maintain and expand large distributed system. It clearly outlines decisions and agreements software architect has to make at the beginning of the project. There are many real life examples bridging concepts with everyday problems. Abundant diagrams and code samples make complex ideas easy to grasp.To me it was very helpful to see how design and development principles are tied in with maintenance and troubleshooting aspects. I also greatly appreciate author’s insight on practices which work for development, QA and DevOps teams.The guide is fun to read and keeps you engaged like a good thriller.it quickly became popular reading at my work and we are looking forward for Book 2.

Worth maybe $15. Way overpriced.

In "Become an Awesome Software Architect", Anatoly Volkhover shares with us his hard-won knowledge from many years in the trenches of enterprise application architecture and development. The book has a practical focus and is intended as a primer and recipe book. This is not the place to go for in-depth theoretical discussions. Also, some of the author's recipes are based on unorthodox viewpoints (e.g his preference for RPC over REST). Justifications are provided, but are not argued at length. I found this refreshing, others may find it maddening. Generally, the recipes are smart, actionable, widely applicable and clearly explained. However, the book is overpriced. Although there is a lot of content packed into this small package, the author ends the book by listing additional topics to be covered in future volumes. For the price, it would have been nice to have had that additional content in a single volume. That said, I do hope that Anatoly will continue writing on these topics. I, for one, am interested in hearing what else he has to say.