際際滷

際際滷Share a Scribd company logo
The De鍖nite 
Production 
Checklist 
An Interview with DevOps
Specialist Nico Duldhardt.
1. Staging 
Environment 
Mimic your production
environment as closely as
possible.
 do not push changes
straight to production.
 use (anonymized) real
world data.
2. CI / CD 
Human errors are the norm, not the exception.
Account for them!
 run tests & linting.
 build & release your containers.
 deploy changes to staging.
 deploy tested changes to production.
Source: https://codilime.com/blog/business-bene鍖ts-of-ci-cd/
3. Error Tracking 
Fixing errors fast requires you to be aware of
them.
 centrally track errors.
 enrich them with metadata.
 receive noti鍖cations.
 collaborate on 鍖xing your software.
4. Rollbacks 
Think ahead of how to undo changes
 rolling back containers is easy.
 rolling back database schemas is not.
A (semi-) automatic process reduces downtime.
Source: https://dev.to/isabelcmdcosta/how-to-undo-the-last-commit--31mg
5. Backups 
Have an insurance in place to save your weekend
plans.
 Document a disaster recovery strategy.
 Back up your data stores.
 Give it a try!
Outlook 
More advanced techniques to hit your goals
(service level objectives) :
 Metrics
 Tracing
 Rolling Updates
 Security Testing
Thanks 
Watch the full video on my YouTube channel
YouTube.com/@tillcarlos.
Reply in the comments: whats your opinion on
this?

More Related Content

A DevOps Guide: 5 Pillars of Professional Deployments from DevOps Expert Nico Duldhardt

  • 1. The De鍖nite Production Checklist An Interview with DevOps Specialist Nico Duldhardt.
  • 2. 1. Staging Environment Mimic your production environment as closely as possible. do not push changes straight to production. use (anonymized) real world data.
  • 3. 2. CI / CD Human errors are the norm, not the exception. Account for them! run tests & linting. build & release your containers. deploy changes to staging. deploy tested changes to production. Source: https://codilime.com/blog/business-bene鍖ts-of-ci-cd/
  • 4. 3. Error Tracking Fixing errors fast requires you to be aware of them. centrally track errors. enrich them with metadata. receive noti鍖cations. collaborate on 鍖xing your software.
  • 5. 4. Rollbacks Think ahead of how to undo changes rolling back containers is easy. rolling back database schemas is not. A (semi-) automatic process reduces downtime. Source: https://dev.to/isabelcmdcosta/how-to-undo-the-last-commit--31mg
  • 6. 5. Backups Have an insurance in place to save your weekend plans. Document a disaster recovery strategy. Back up your data stores. Give it a try!
  • 7. Outlook More advanced techniques to hit your goals (service level objectives) : Metrics Tracing Rolling Updates Security Testing
  • 8. Thanks Watch the full video on my YouTube channel YouTube.com/@tillcarlos. Reply in the comments: whats your opinion on this?