Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architectures

Great book
This is a great book. I enjoyed it far more than the fundamentals book. If you can master Kleppmann for the infrastructure grounding and this for real life use cases you’ll be well on your way. I really appreciated the fact that they point out tradeoffs *everywhere*. That’s part of the job and it can be hard to see them when we gravitate toward one option because it feels right or because of groupthink.Some minor criticisms:* the Data Mesh chapter felt tacked on, underdeveloped and in some places was incorrect or at least confusing (e.g. it says data warehouses cause loss of domain partitioning which is not true)* The book talked about tradeoffs so much it wasn’t always clear why they thought taking a certain path would hurt a certain quality attribute. “Because there is more coupling scalability will suffer”, etc. Perhaps. But explaining how would be great. The book hints at some relationships between quality attributes. If that were more well-developed that could be a way to better understand these statements too.* While I’m sure it wasn’t meant for effect, there is only one woman in the story portions, she is somewhat naive, a bossy PITA and has to be dragged along most of the time. Having the *only woman* play that role stood out to me as potentially insensitive.

Used product was essentially new and never been used.
Book arrived in excellent condition.

Good book, but title is misleading
This book provides a good overview of how to refactor a monolithic application into microservices, and thus also includes a good introduction to microservices architecture. The book is well written, easy to read, and well structured. Despite having multiple authors, the book is fairly consistent throughout, both in style and content.The book does not, however, cover any “hard parts”. It only covers the basics, often superficially. Naming the book “Migrating Monoliths to Microservices” or “Microservices Architecture 101” would have been more appropriate.That is not a criticism of the contents, which is valuable if that is what you are looking for. But the title is misleading.The biggest weakness of the book is its coverage of distributed data stores. This is probably the hardest part of distributed systems, and this book barely covers this topic at all.

great book
great content, worthy of Orielly .. very easy read for someone very familiar with all the concepts .. great reference and very practical – really cool .. thank you i bought three more titles because of this one 🙂

Caminhos certos, mas cada um com suas consequências e “trade-off’s” específicos. O desafio de decidir por uma abordagem de arquitetura para suportar uma operação de negócios é apresentada de forma bastante interessante. Baseada num cenário verossímil, e muito comum nas empresas. Vale a leitura.

If you have to buy on book on re-engineering software monolith, I would recommend that one: very practical, get a 8h coaching session by reading this book for 50 dollars! A bargain!

I am following this book to improve my software architecture skills, and I find here not only a lot of good advice but also the “right words” to express many of my concerns as a Software Architect when trying to communicate them e.g. stakeholders. Most of the time I know why and how, but struggle to find the proper analogies and “translations” of the technical reasoning to contexts where what matters is the business perspective (and terminology). The book so far is supporting me a lot in this aspect. At a more practical level, it is also making me review my existing architectures with new perspectives and ideas.