devops

About

  • Version control

  • Continuous delivery

  • Continous integration

  • Monitoring

  • Containerisation and container management

  • Build tools

  • Dependency management

  • Releases

What is devOps?

  • https://www.javacodegeeks.com/2018/05/devops-a-methodology-to-learn-from.html

  • https://herbertograca.com/2018/04/02/the-containerization-chronicles/

  • https://www.youtube.com/watch?v=_I94-tJlovg

  • https://www.javacodegeeks.com/2018/07/devops-vs-sre-difference.html

  • https://www.youtube.com/watch?v=JHoy3lDZOfY&t=66s

  • https://www.edureka.co/blog/puppet-tutorial/

  • https://medium.com/hackernoon/the-2018-devops-roadmap-31588d8670cb

  • https://www.digdeeproots.com/articles/devops-series-unclogging-the-pipelines/

ci/cd

Developers practicing continuous integration merge their changes back to the main branch as often as possible. By doing so, you avoid the integration hell that usually happens when people wait for release day to merge their changes into the release branch.

Continuous delivery is an extension of continuous integration to make sure that you can release new changes to your customers quickly in a sustainable way. This means that on top of having automated your testing, you also have automated your release process and you can deploy your application at any point of time by clicking on a button.

Continuous deployment goes one step further than continuous delivery. With this practice, every change that passes all stages of your production pipeline is released to your customers. There's no human intervention, and only a failed test will prevent a new change to be deployed to production.

https://semaphoreci.com/blog/cicd-pipeline

Glossary

  • https://xebialabs.com/glossary/

  • https://medium.com/@DZoneInc/48-devops-terms-you-should-know-a-devops-glossary-37e60fd23752

  • https://itsvit.com/blog/devops-glossary-78-basic-devops-terms-in-simple-words/

issues

  • https://www.youtube.com/watch?v=52ht63dMQ1g DevOps is dead. Embrace platform engineering.

    • platform/sre team instead of one team creates looks after it

Last updated