5 points how google sees devops culture
reduce organisation silos, accept failure as normal, implement gradual change, measure everything, leverage tooling & automation
1 reduce organisation silos:
- Development teams, infrstructure teams, need to start thinking and communicating as one team and move towards actually forming one team
- Developers need to have knowledge about operations and operations need to have knowledge about development
2 accept failure as normal:
- Implement fail-safes from the start during coding and deployment and see the occurence or failures as a certainty in the long term
- Do not play the blame game when a failure does lead to larger problems but see how a fail-safe can be implemented
3 implement gradual change:
- Make small changes in code easier by using automation so that a code change does not lead to a heap of work every time
- Reduce the need for hellish crunch months having huge changes right before releases
4 measure everything:
- Automatic monitoring for security, capacity or other incidents is essential to implement gradual changes fast and solve these incidents
- Detailed monitoring brings new insights into the usage of different application features and user interests
5 leverage tooling & automation:
- Use automation tools to help the other points come into reality
- Standardize tools and working methods to bring development and operations close together
what is a well known methodology + explanation
Well known methodology is Agile which is most recognised for the tooling that automates the entire process of a application development and operations
what is a devops pipeline
a devops pipeline is a Sequence of implemented automated steps and tools
give examples of popular on-premise tools
jenkins an open-source system, or azure devops server a system by microsoft
give the steps in a pipeline
Plan, code commit & automation, static code analysis, build, unit test, integration test, other test stages, containerize & store, deploy, monitor
