Transitioning to Dev Ops requires a change in culture and mindset. At its simplest, Dev Ops is about removing the barriers between two traditionally siloed teams, development, and operations. In some organizations, there may not even be separate development and operations teams; engineers may do both. With Dev Ops, the two teams work together to optimize both the productivity of developers and the reliability of operations. They strive to communicate frequently, increase efficienc...
Transitioning to Dev Ops requires a change in culture and mindset. At its simplest, Dev Ops is about removing the barriers between two traditionally siloed teams, development, and operations. In some organizations, there may not even be separate development and operations teams; engineers may do both. With Dev Ops, the two teams work together to optimize both the productivity of developers and the reliability of operations. They strive to communicate frequently, increase efficiencies, and improve the quality of services they provide to customers. They take full ownership for their services, often beyond where their stated roles or titles have traditionally been scoped by thinking about the end customer’s needs and how they can contribute to meeting those needs. Quality assurance and security teams may also become tightly integrated within these teams. Organizations using a Dev Ops model, regardless of their organizational structure, have teams that view the entire development and infrastructure lifecycle as part of their responsibilities.In this book, we introduce the Dev Ops culture, and the tools and techniques under this technical cultural umbrella. We explain microservice, containers, Docker Container, Kubernetes, etc., and the significance of these in adopting the Dev Ops culture for successful software development.
