Five Principles of Software Deployment

In yesterday’s post, 2 out of 3 ain’t bad?!?, I wrote about a survey which suggested that 2 out of 3 developers don’t have a staging environment.

In my opinion, this is a violation of one of the basic principles of software deployment - Environments should be consistent.

In this post, I present my Five Principles of Software Deployment. Over the next couple of weeks, I’ll take a closer look at each one and provide advice on how they can be achieved.

The Five Principles of Software Deployment

1. Builds should be repeatable
2. Environments should be consistent
3. Packages should be autonomous
4. Releases should be easy to do and undo
5. Failures should be obvious

Stay tuned for more details.

3 comments ↓

#1 Principle #2 - Environments should be consistent (Part 2) — Sauers Technologies on 01.27.08 at 9:32 am

[…] my previous post, I discussed the second of The Five Principles of Software Deployment, namely that Environments should be consistent. In that post, I looked at how developers could […]

#2 Principle #3 - Packages should be autonomous — Sauers Technologies on 02.15.08 at 8:37 am

[…] post discusses the third of The Five Principles of Software Deployment: Packages should be […]

#3 Principle #4 - Releases should be easy to do and undo — Sauers Technologies on 04.19.08 at 6:46 am

[…] a bit of a break to meet some client deadlines, I’d like to continue the series The Five Principles of Software Deployment. This entry discusses the fourth principle in that series: Releases should be easy to do and […]

Leave a Comment