After reading for interesting information in the web about DevOps I have learned a lot about its area and about for what its used.
DevOps is the practice of operations and development engineers working together in the entire service lifecycle, from the design through the development process into production support. It is also characterized by operations staff making use many of the same techniques as developers for their systems work.
It also is a new term emerging from the collision of two major related trends, it sprang from applying Agile and Lean approaches to operations work, but also from the understanding of the value of collaboration between development and operations staff throughout all stages of the development lifecycle when creating and operating a service, and how important operations has become in our increasingly service-oriented world.
Some call DevOps as being “developer and operations collaboration,” or it’s “treating your code as infrastructure,” or it’s “using automation,” or “using kanban,” or “a toolchain approach,” or “culture,” or a variety of seemingly loosely related items all because the discussion around it covers a lot of ground.
DevOps is not simply implementing a set of tools to use; some people only use the automatization without the thinking and theory.
DevOps is a little tricky, but the most important is that the people that use it should understand and practice that software isn’t done until it’s successfully delivered to a user and meets their expectations around availability, performance, and pace of change.
In the end its aim its to provide a faster and reliable software product development and careful implementation with the use of the assistance of automation.
It also helps with: finding pain points inside the development operation system. It provides reliable strategies, reduces the amount of risk, and reduces the failures in new launches.
References:
https://theagileadmin.com/what-is-devops/
https://www.atlassian.com/devops
Testing 