Sign in with Facebook
Loading...
56th out of 86 books
—
151 voters
Release It!: Design and Deploy Production-Ready Software (Pragmatic Programmers)
Whether it's in Java, .NET, or Ruby on Rails, getting your application ready to ship is only half the battle. Did you design your system to survivef a sudden rush of visitors from Digg or Slashdot? Or an influx of real world customers from 100 different countries? Are you ready for a world filled with flakey networks, tangled databases, and impatient users?
If you're a deve...more
If you're a deve...more
Paperback, 326 pages
Published
April 6th 2007
by Pragmatic Bookshelf
(first published March 30th 2007)
Friend Reviews
To see what your friends thought of this book,
please sign up.
Community Reviews
(showing
1-30
of
699)
I was pretty sure I'd like it when, early on, I came across the following quote:
"...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
"...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
This book is fantastic.
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
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
I think this might be the best Pragmatic Programmers book since the original The Pragmatic Programmer From Journeyman to Master. It was well-written and well-organized, and addressed the operational and maintenance issues that are often ignored or glossed-over in software development books.
The detailed "from-the-trenches" stories to illustrate the author's points were very engaging and informative. He describes situations where he had to investigate the causes of software failure, and how the pr...more
The detailed "from-the-trenches" stories to illustrate the author's points were very engaging and informative. He describes situations where he had to investigate the causes of software failure, and how the pr...more
Awesome! Must read for anyone who is(or wants to be) exposed to designing and running largely distributed(enterprisey) systems. In fact I'd recommend it to any engineer.
The book has plenty of real life stories, as well as good suggestions on how problems could have been mitigated beforehand.
Some of my takeaways:
- Resource pools as a way contain failures within broken integration points
(properly cooked: low contention, configurable, with timeouts and handling 'no free resource found' case 'schedu...more
The book has plenty of real life stories, as well as good suggestions on how problems could have been mitigated beforehand.
Some of my takeaways:
- Resource pools as a way contain failures within broken integration points
(properly cooked: low contention, configurable, with timeouts and handling 'no free resource found' case 'schedu...more
Vigorous style, plenty of samples, reasonable propositions.
Essentially, this book includes following information:
- real-world samples when a small thing causes a huge system to crash
- ways to quickly get the system back to work
- troubleshooting methods for big distributed systems
- list of possible dangers and how your system can deal with them
- rules for making production-ready systems
- work with dependencies in code
- patterns and practices for developing release-ready software
- etc.
Conc...more
Essentially, this book includes following information:
- real-world samples when a small thing causes a huge system to crash
- ways to quickly get the system back to work
- troubleshooting methods for big distributed systems
- list of possible dangers and how your system can deal with them
- rules for making production-ready systems
- work with dependencies in code
- patterns and practices for developing release-ready software
- etc.
Conc...more
I don't know why I only now got this book in my hands. It reveals so many things that I was missing in my development. It is full of aha! moments and realisations of the things that I have missed with great ideas of how I can improve. The book, in some aspects feels slightly dated - mainly with the technologies mentioned (evident focus on session state and relational databases) yet I can't think of a modern system that takes even a fraction of the applicable advice from the book regardless of te...more
I need to start by saying that this is one of the best technical books I have ever read. To me, it's easily as enjoyable and useful as Code Complete, The Pragmatic Programmer, or The Mythical Man Month. If you're a sysadmin, an architect, or a developer that works with medium-to-large-sized systems, then do the following:
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 i...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 i...more
If you are in the business of making software systems, odds are that you might have heard about Nygard's book. People have raved about it since it was published in 2007.
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
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
Highly recommending this book for those working on more complex software systems. The book touches several fields of software development discussing what can go wrong and how to avoid failures. Having possible failures and strategies to avoid them makes the softwares evolution significantly different than thinking about an ideal path. I believe following some of the recommendations of this book will result in a more changeable and robust software products.
Great companion to Continuous Delivery. Covers more of the development and architecture side of things and, again, should be required reading for every architect and senior developer. Don't agree with everything he says about database deployment; declarative development is much more useful than trying to code state transitions, especially when structure is in transition.
I've released a lot of sites over my career, and I still spent this entire book highlighting passages and making copious notes about ways to improve my project's architecture and release process.
Great references, good examples. I also liked how it had little 'things to remember' parts.
Be cynical!
Be cynical!
A must read for everyone in software development. Especially for those working on HA systems.
Good reading for architects, Application Operations team etc.
Discuss about different design considerations for Operation readiness.
Discuss about different design considerations for Operation readiness.
Excellent study that really makes you think differently about the way reliable software is built.
The best technical book I've read in a long, long time.
awesome book!
Release It! is about building software to run in today's networked, distributed environments. Such software must be failure tolerant and scalable -- reslilient, in a word. He describes "anti-patterns", liberally illustrated with stories from his personal experience, and then counters them with patterns of development and release that will provide stability, scalability, and failure tolerance. A must read for anyone engaged in or considering developing for "the cloud" or web-based applications in...more
A must-read book for any software developer.
Michael nails it.
A practical guide to developing software applications for the Internet, illustrated with numerous, often entertaining, cautionary tales. My favorite is the story of the airline reservation system that seized up nation-wide, due to an unhandled SQLException. From his experience trouble-shooting such problems, Nygard extracts a list of stability and capacity "anti-patterns" that lead to system vulnerabilities; and, conversely, a list of "patterns" that exemplify robust design.
pretty interesting book on software development, with descriptions of patterns & anti-patterns that affect stability, performance, etc.
I quite enjoyed reading this book, even if it did scare me a little with some potential problems I need prevent blowing up in my face. If you intend on your code being used in production I strongly suggest you read
I just re-read this for the second time and I found it to be even more useful. If you are creating a new enterprise solution I would highly recommend that you read this book before starting. It is likely to save you from late night conference calls and emergency plane trips.
I couldn't stop reading.
A really inciteful book. Gave me lots to think about even though I'm not a web developer, just some of the processes and examples provided were very good. Even if you get only a couple of things from this book, it's worth reading.
Nov 09, 2008
Doc
rated it
4 of 5 stars
Recommends it for:
developers, qa, project managers
Shelves:
technology,
agile-lean
Clear and specific instructions on how to deploy software. A must-have toolbook for software developers, especially those who think deployment is someone else's job.
I read this book in like 2 days. I need to re-read it. Great book.
After you create software people start using it...then the real problems can begin. This book contains a wealth of ideas from the real world on how to make software stable, transparent, and adaptable. I found it very practical.
Some of the issues he described I had faced before and the book gave me new ways to think about the problems in the future.
Only complaint is that some sections are way too Java and web centric and those sections were a slog to read through.
Some of the issues he described I had faced before and the book gave me new ways to think about the problems in the future.
Only complaint is that some sections are way too Java and web centric and those sections were a slog to read through.
There are no discussion topics on this book yet.
Be the first to start one »
The ideas from the book now alive :)
Dec 27, 2012 08:05am