The advice in this blog post by Kent Langley resonates with my experiences launching Web infrastructures of all types, large and small. Deploy early and often, automate your deployments, use version control, create checklists, have a rollback plan -- these are all very sensible things to do.
I would add one more very important thing that seems to be missing from the list: have an extensive suite of automated tests to check that your deployment steps did the right thing. Many people just stop at the automation step, and don't go beyond that to the testing step. It will come back to haunt them in the long run. But this is fodder for another blog post, which will be coming real soon now ;-)
Tuesday, July 14, 2009
Kent Langley's '10 rules for launching a web site'
Subscribe to: Post Comments (Atom)
Modifying EC2 security groups via AWS Lambda functions
One task that comes up again and again is adding, removing or updating source CIDR blocks in various security groups in an EC2 infrastructur...
This post is a continuation of my previous one on " Running Gatling tests in Docker containers via Jenkins ". As I continued to se...
For the last month or so I've been experimenting with Rancher as the orchestration layer for Docker-based deployments. I've been pr...
Here's a good interview question for a tester: how do you define performance/load/stress testing? Many times people use these terms inte...
Wait? Grig are you endorsing automated testing? Crazy!
Thank Grig. I would whole-heartedly agree with the automated testing suggestion. However, I've tried to bake this into projects time and time again only to be over-ruled by the developers, their bosses, or the clients themselves who did not want to pay for the effort up front. Shame.
I think they do not understand the hidden costs later. I explain, but it rarely resonates.
Post a Comment