- Reducing the sdlc life cycle time .
- Two-way collaboration between development and operation teams
- Two-way collaboration between Development and Operation teams.
- Turnaround of Ops tasks in minutes to hours, not days to weeks.
- Strong involvement from developers; otherwise, it’s back to Devs versus Ops.
- Operations people need development skills—at least Bash and Python.
- Developer people need operational skills—their responsibilities don’t end with writing the code, but with deploying the system to production and monitoring alerts.
- Automation, automation, automation: you can’t accurately automate without Dev skills, and you can’t correctly automate without Ops skills
- Ideally: self-service for developers, at least in terms of deploying code. Can be achieved via CI/CD pipelines.
- GitOps.
- Bidirectional everything between Development and Operations (tooling, knowl‐ edge, etc.).
- Constant collaboration in design, implementation, deployment—and yes, auto‐ mation—can’t be successful without cooperation.
- if it isn’t automated, it’s broken.
- Cultural: Hierarchy < Process.
- Microservices > Monolithic.
- The continuous deployment system is the heart and soul of the software team.
- There are no superheroes.
- Continuous delivery isn’t an option; it is a mandate.
You can become a powerful DevOps practitioner by learning only a small subset of python