DZone
DevOps Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > DevOps Zone > Why You Shouldn't Have to Deploy Overnight

Why You Shouldn't Have to Deploy Overnight

Mitch Pronschinske user avatar by
Mitch Pronschinske
·
Oct. 17, 11 · DevOps Zone · Interview
Like (0)
Save
Tweet
10.57K Views

Join the DZone community and get the full member experience.

Join For Free

Are you still doing deployments at 3:00am?  If you are, you should have taken a look at Brian Crescimanno's post: "Why are you still deploying overnight?"

Whatever you call the process of turning your development codebase into a live, production application, I sincerely hope you’re not living in the Stone Age and doing it in the middle of the night under the guise of avoiding customer impact. Unfortunately, if my past experiences, and the experiences of many I’ve spoken to, are the norm, you very likely are.  If your strategy to avoid customer interruption is based solely on trying to avoid your customers, you’re setting yourself up for even more headaches and long-term failure. --Brian Crescimanno

 



Brian asserts that if you're doing these overnight deployments to avoid your customers during the initial release, then it's probably indicates that one or more things are broken in your process.  Here were the problems he listed with overnight deploys:

  • Problem 1: You presume there will be problems that impact availability.  
  • Problem 2: You’ve got a complicated process and you’re sending over-tired, over-worked people to deal with it.
  • Problem 3: You have no means of doing a phased rollout or a quick rollback.

So the moral of the story, if you buy in to his assessment, is that you should be getting some sleep at night instead of deploying.

Source - http://briancrescimanno.com/2011/09/29/why-are-you-still-deploying-overnight/
Image Source - http://www.flickr.com/photos/zenera/28726053/






Brian (software) application Rollback (data management) POST (HTTP) Production (computer science) Release (agency) Moral IT Norm (artificial intelligence)

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Testing Under the Hood Or Behind the Wheel
  • Federated Schema Design
  • Modern REST API Design Principles and Rules
  • Portfolio Architecture Examples: Retail Collection

Comments

DevOps Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo