Release It!: Design and Deploy Production-Ready Software
A single dramatic software failure can cost a company millions of dollars - but can be avoided with simple changes to design and architecture. This new edition of the best-selling industry standard shows you how to create systems that run longer, with fewer failures, and recover better when bad things happen. New coverage includes DevOps, microservices, and cloud-native
I really just can't say enough about this book. It's required reading. If you're responsible for code that runs on networked production systems, failing to read this book should be a fireable off ...more
Release It! is one of the most important books I think programmers can read, easily as important as the oft-cited classics like The Pragmatic Programmer or the GoF book. Release It! isn't about writing super-spiffy code, or object-oriented design, but it should drastically affect how professional programmers write their code. It focuses on what engineers need to do to get their software into a state where it can actu ...more
1. Stop reading this post
2. Order this book from your library or buy it from The Pragmatic Programmer's web site
3. Owe me a pint :D
What The Book Is Really About
Actually, there ...more
But make no mistake, this is not a pr ...more
This book is a perfect mix of lots of useful technical insights, practices and recommendations got from the author's hard-earned experience combined with some of the soft-skills you need to make your software and its maintenance (which as the author states costs more than the ...more
I was initially a little taken aback because I was expecting the book to have more details about how you prep for a release, how you come up with a plan, your checklist if you will. But it is more about operat ...more
Now, it's pretty dated in a few places. It's from 2007, when the term DevOps wasn't even widely used yet. At the same time it's interesting to see how a lot of it still holds.
There are too many references to JVM-speficic issues. I don't think this ruins the experience for readers working outside the JVM, but it's strange seeing cas ...more
A seasoned developer would have probably been learned some of the advice the hard way. Nonetheless I've picked up a lot of wisdom ...more
Software is not just about creating code, it is about releasing it, operating it, and administering the system in production. Once this is understood, the way someone develops software changes drastically. Compatibility, monitoring, observability, etc start to become part of the design and we start to embrace change and adaptability.
This book gets into the specificity of ...more
Armed with a thread dump, the application is an open book, if you know how to read it. You can deduce a great deal about applications ...more
What would these kind of systems with a focus for real-world use look like? He starts by outlining stability anti-patterns. These are bad practices often found in the design of systems which render it more fragile, a ...more
It's a whirlwind tour through designing code that behaves well in production, the many ways interaction between multiple systems can fail, deployment styles that avoid scheduled downtime, and case studies to demonstrate the surprises that happen in the real world.
For those new developing and deploying production software the pace might be hard to follow, but those with a bit of experience under their belt will find this triggers ...more
The book predates all the dev-ops hype, but still gives you tons of suggestions how to build a robust, scalable and easy-to-understand-when-something-goes-wrong application: think about failure, every possible component WILL fail in production. Every possible 'joint' like external system interaction will be broken. Every possib ...more
What this book is actually about is the overall quality of software products (looked at from very various perspectives) and how do different types of flaws impact the product / service in the end. As you can see, this is a far wider (& more generic) topic - if this is what you're l ...more
I would set 10 starts rating out of 5 possible if I could.
Definetely recommend it to any software developer or system engineer.
It takes another approach on good practices of software architecture: it considers more than just classic quality attributes, and it makes you think you to architect your system in a way that's not only reliable and with good quality, but also easy to operate with. Concepts such as evolutionary architecture, adaptable architecture are reivewed throughout the chapters on the last section. In particular I enjoyed ...more
This book does a great job of explaining the problems you face running code in the real, high-scale world, walking you through war stories and asking how outages could have been prevented. Then expl ...more
That being the case, it had been on my to-read list for a while, but without any urgency. Then I went a conference where I heard two sessions with Michael Nygard presenting his ideas. After that, I knew I had to get hold of the book straight away.
Release It! is something as rare as a book which is groundbreaking while stating the ...more
I still believe the book contains lots of useful information, but they are rather generic, you won't find any real code examples, information about edge cases and so on. I was aware of that prior to buying this position, but I've got a feeling that many information are repeated over ...more
Let's be frank: I'm biased, because the author is a friend and colleague, and I know some of the stories he tells from personal experience (I'm even in one of them, anonymously).
Nygard writes very well, taking complex concepts and breaking them down into their components, and leaving the reader with essential takeaways of the patterns that create problems and the patterns that can prevent them. The term is never used in this book, but the concept of DevOps underlies the ...more
"...sites are now expected to be available 24 by 7 by 365." Footnote: "That phrase has always bothered me. As an engineer, I expect it to either be '24 by 365' or '24 by 7 by 52.'"
This book has a lot of good information on building web applications that can withstand very high load. It is well-written, and he does a very good job of explaining the reasons why different approaches are particularly good or bad.
I have n ...more
Goodreads is hiring!
Learn more »