Become an Awesome Software Architect: Book 1: Foundation 2019

by Anatoly Volkhover

Great software architects aren’t born. They are a product of decades of building real-life solutions and relentless learning. They become really good at their trade closer to the retirement age. But most startups are fostered by young entrepreneurs who dare to try but lack the experience. They also lack the $$ to hire a silver-haired architect to join their team from day one. Left to their own faculties, the entrepreneurs and their engineering teams quickly get on the path of learning from their own mistakes. Eventually, they discover this is the most expensive way of learning. Over time they get better, and some become the true masters of the craft – but way too late to make a difference for their early-day projects.

This book is meant to break the vicious circle. It isn’t a textbook, at least not in the traditional sense. It is a business-centric practical guide to software architecture, intended for software engineers, technology executives, students of computer science, and tech-savvy entrepreneurs who want to de-risk their entrepreneurial endeavors or to fast-track their careers in software engineering. The recipes in this book are highly practical, battle-tested, and current for building mid- to large-scale systems in 2019.

Genres: Architecture, Programming, Computer Science, Technology

190 pages, Paperback

Published October 7, 2019

Reviews

[Johann Lilly · Rating 5 out of 5]

A clear introduction to software architecture with up-to-date technologies and modern code examples using TypeScript. It is worth the read, as well as re-reading individual sections when the subject arises in practice in your organization.

[Ivan Chernov · Rating 4 out of 5]

Это хорошая книга начального уровня. Больше всего мне понравилось, что она полностью opinionated - так делать хорошо, так делать плохо. Что входит в хорошо:
- типизирование строгие языки > отсутствия типизации
- бизнес логика - это главное, а хранение данных должно быть завязано на него
- лучше делать event based системы, чтобы было гибко расширять

и так далее, жалко, что вторую автор так и не написал.

[Denis Romanovsky · Rating 3 out of 5]

Some good prescriptions, but too shallow and not enough for a book on architecture. Still can be a good thing for a middle level engineer.

[Srinivasan Nanduri · Rating 3 out of 5]

Too primitive. I don’t know if I agree with some of the key advices made in the book but there are a few learnings noted

[Ionut Penciuc · Rating 3 out of 5]

It provides a nice summary over a lot of important aspects but doesn’t delve into depth in any of them. Too shallow for a Software Architect, much more appropriate to the middle experienced fellows.