reviews
Jun 02, 2008
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 ap 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 ap More...
Dec 18, 2009
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 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 More...
Nov 06, 2011
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 prac 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 prac More...
Jun 04, 2010
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
Wh 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
Wh More...
0 comments
like
(1 person liked it)
Sep 11, 2011
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 groundbreaki 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 groundbreaki More...
Jan 12, 2012
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.
Dec 28, 2011
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.
Aug 25, 2009
Good reading for architects, Application Operations team etc.
Discuss about different design considerations for Operation readiness.
Discuss about different design considerations for Operation readiness.
Oct 12, 2008
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.
Sep 18, 2011
pretty interesting book on software development, with descriptions of patterns & anti-patterns that affect stability, performance, etc.
Jul 01, 2011
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.
Jan 10, 2011
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
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.
Jul 12, 2009
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.
Feb 11, 2012
Feb 08, 2012
Feb 03, 2012
Jan 31, 2012
Jan 27, 2012
Jan 26, 2012
Jan 25, 2012
Jan 22, 2012
Jan 18, 2012
Jan 18, 2012
Jan 17, 2012
Jan 17, 2012
Jan 16, 2012
