InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Book Excerpt and Review: Release It!

Posted by Ryan Slobojan on Dec 27, 2007

Sections
Enterprise Architecture,
Operations & Infrastructure,
Process & Practices,
Architecture & Design,
Development
Topics
Delivering Quality ,
Architecture ,
Performance & Scalability ,
Stories & Case Studies ,
Java ,
.NET ,
Agile ,
Enterprise Architecture ,
Deployment / Datacenter ,
Ruby
Tags
Book

Release It!: Design and Deploy Production-Ready Software by Michael Nygard discusses what it takes to make production-ready software, and explains how this differs from feature-complete software. On his website, Nygard described the motivation behind writing this book:

This book comes from my extensive experience living with systems in production. I've often been the one to get woken up at three in the morning when some supposedly 24x7 system goes down.

Other books on design and architecture only tell you how to meet functional requirements. They help your software pass QA. In "Release It!", I'll show you how to make your software production ready. If you don't want to wear an electronic leash, you need this book.

Read Book Excerpt and Review: Release It!

From the article:

InfoQ: There seems to be a tension between the up-front work involved in creating production-ready software and the Agile idea that you do something only when you need to, and refactor as necessary - what are your thoughts on this?

Michael Nygard: As an agile developer, I struggle with this tension myself. I don't have a perfect answer for resolving it, but I think there's a parallel here to good object-oriented design.

Once you've written some code and some unit tests that pass---regardless of which came first---you refactor the code to improve the design. "Improve". Well, what does it mean to improve the design? Doesn't that mean you have to have some notion of "better" and "worse" as it applies to OO design? It does, and that's where Martin Fowler's "code smells" from Refactoring come in. "Code smells" are a qualitative way to talk about better and worse design without getting all hung up on metrics.

I think there's something similar for the architecture. For me, a remote call without a timeout is an "architecture smell". So is a SOAP call or a REST GET that tries to fetch all orders for a customer, without applying a limit.

So, while I do not subscribe to big design up front, or "big architecture up front", I do believe in defining the boundaries within the system, designing failure modes into it, and eliminating "architecture smells" as we encounter them.
  • This article is part of a featured topic series on Agile
Superb book by Stefan Tilkov Posted
Re: Superb book by Mirko Nasato Posted
It sounds very interesting by hernan garcia Posted
Excellent Article by Ranjiva Prasad Posted
  1. Back to top

    Superb book

    by Stefan Tilkov

    Michael's book is among the best IT books I've read in the past five years. Thoroughly recommended!

  2. Back to top

    It sounds very interesting

    by hernan garcia

    As the lead of an agile team that is some time wake up at three in the morning I really feel the urge to read this book, just adding it to my queue.

  3. Back to top

    Excellent Article

    by Ranjiva Prasad

    I will be buying this book as a belated Xmas present for everyone on my team. I have lost count of the number of times that I have been woken up at 3am in the morning, because my developers did not think about how an application they built would behave in a production environment. The extra sleep I will get will far offset the costs of buying 20 copies of this book!

  4. Back to top

    Re: Superb book

    by Mirko Nasato

    +1

    An excellent book indeed, and a needed one. I really think "the industry" (i.e. we developers) need to put more focus on how applications behave in production.

    Maybe part of the problem is also that many developers will never get awakened at 3am anyway, because operations will be someone else's job, and they don't get a chance to learn much about this very important aspect of software development.

    I think it would be interesting to investigate "organisational" patterns as well that can help improve application robustness, in addition to the technical design patterns.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.