Release It!: Design and Deploy Production-Ready Software

It’s not a bad book, I would even say it’s a great one. It’s just not what I expected which was something more agnostic while it’s kinda tied to backend as a theme.Still the insight of the author is nice but I would probably recommend it to someone working in backend mostly.

I was looking for a "go to guide" that basically encapsulates all of the concepts of Continuous Delivery and the intersection of Agile Ways of Working, xTreme Programming (XP) and modern DevOps practices applied to Cloud and Service Ecosystems. This came up as a suggestion via a couple different searches. (not Google) I then read the table of contents as I was in a hurry, bought and downloaded... only to realize... Oh... It's Nigel... Of course it has everything I need. Well done, Nigel!

Michael has a talent for injecting just enough humour into his writing to make it engaging without sacrificing technical detail or critical observations. This books contains valuable lessons learnt the hard way from real world mishaps. Anyone who has been developing software long enough will identify with the "ohnosecond" that follows pressing [enter] on a poorly thought through action. Revel in Schadenfreude if that is your thing but remember "if it can go wrong, it will go wrong" and none of us are immune. Consider this book as both prophecy of your impending doom, but also as a manual of the many traps you will encounter along the way and how to disarm them.

Well written because it is clear and engaging. It articulates many things about stability and failure modes that need to be said. Few will remember a checklist but the way anti patterns and patterns are shared with experiences will make the concepts digestible and committed to memory. It reads like a compilation of post mortem with thoughts arranged systematically. If you want to build a culture of engineering this book is a great read.

loved some of the more philosophical sections at the end, dealing with complexity, architectural and organizational principles. reading through some of the case studies was painful as each incident describes real life catastrophes that csn happen to any tech org

From start to finish I couldn't put it down. Everything I had learned to date in my career was in there and much much more. I've saved years reading this book.An absolute master class in software engineering.

I like how the stories is told and guide theories to practice, with numerous insight about real cases.

From a 35 year software professional...one of the best, most thought provoking books on the subject of software engineering I've read in years. It's not about releasing software so much as how to design software that you can feel confident in releasing. Much insight, not just into real-life problems, but guidance on ways to solve them. Changed my perspective and my designs for the better. Highly recommended.

Bought this book off the recommendation of Jim Webber - simply wonderful book on engineering.The writing is amazing - the author knows how to capture the attention of the reader, and more importantly, knows how to raise an engineer to a level of professionalism required in the field through the various horrible engineering stories that could've been avoided by being careful about development.Great book that made me be more self-aware of the importance of little things - little things that can crash a whole distributed system.Prolly a must-read in the literature.

Interesting book to understand typical problems with distributed systems. Briefly touches a variety of different aspects which add up to the robustness of a system. Reading this book might give you a few ideas on how to think about specific problems, and maybe a few new techniques to have some further reading about. It is not too specific about any technology, just a great overview of the broad topic of how to better maintain a living distributed system.

Interesting book to understand typical problems with distributed systems and how to best tackle them. Very useful for devops or would be architects

If you are just starting your career in software development this might be useful. However, anyone has worked in a good agile environment this books brings no new ideas. A little disappointing.

El libro es un batiburrillo de "habría que hacer ésto" y "habría que hacer lo otro", pero sin precisar el cómo en la mayoría de los casos. Los capítulos más interesantes son el 4 y el 5.Es un libro de 2017. Hoy en día se usan tecnologías distintas, los que lo compren para estar al día que lo tengan en cuenta.