What is DevOps?
The term “DevOps” comes from the fusion of the words “Development” and “Operations”. Essentially the main objective of the DevOps philosophy is to reduce the silos between the Development and Operations departments in order to improved the delivery of software products.
DevOps aims to motivate collaboration between two areas that traditionally have been looked as two different entities with different objectives. But this not only applies to just these two, QA and InfoSec play an important role and hence suit perfectly into the application field.
At the end of the day, the key element behind DevOps is “collaboration”. Developers, operation staff, testers and information security officers, all working together as part of the same team for the same goal.
Culture, Processes and Tools.
DevOps is not a person, neither a position nor a department. Its implementation is not about hiring a “DevOps Engineer”, but is a culture that includes both technical and non-technical staff, from the CEO of the company to the junior developer.
Another key component of DevOps is “Automation”, but to be able to automate, there has to be something to be automated. These are the processes which need to be defined taking into account the roles and responsabilities of all the involved people.
And finally there are the tools, which are pieces of sofware that engineers will implement in order to support the workflows produced by the collaboration. Tools will allow to execute code testing, track code changes, deploy the application and monitor its performance.