The Bare Bones Guide To DevOps
The Bare Bones Guide To DevOps
Join the DZone community and get the full member experience.Join For Free
Learn more about how CareerBuilder was able to resolve customer issues 5x faster by using Scalyr, the fastest log management tool on the market.
DevOps is the result of coming together of two major concepts of Development and Operations.
In this practice, we see operations and development engineers collaborating until production support, beginning from design and the entire development process.
DevOps also entails operations staff using many similar methods as developers during their work.
These methods can include the use of source control, testing, taking part in an agile development process, among others.
In DevOps scenario, sub-disciplines of system administrators are not segregated.
Although 'Dev' implies developers particularly, its span is much broader, including all the personnel concerned in the development of a particular product. Therefore, quality assurance also falls under it.
Included under 'Ops' are system administrators, systems engineers, operations team, DBAs, release engineers, security professionals, network engineers, among others.
The ideal explanation for DevOps is usage of parallel method to agile development. Agile development constitutes four layers. They are Agile Values, Agile Principles, Agile Methods, and Agile Practices.
Agile Values is the underlying philosophy of the Agile Manifesto. Agile Principles refers to the considered approaches supporting the Agile Manifesto. Agile Methods includes the very precise process deployments of the principles. Agile Practices are the very specialized strategic tools that need to be used along with agile implementations.
DevOps emerged as the need arose for innovation in technology work's systems side. It is a legacy of the Agile System Administration drive and the Enterprise Systems Management (ESM) drive. Therefore, it is not just about the tools being employed.
DevOps specialists believe that beginning work in iterations with lack of proper collaboration will not work out as well as planned.
In the end, DevOps is inclusionary, where all the members responsible for creating a system are an integral part of it. They include business persons behind the system, developers, members of the operations team, networking staff, people of the security team, and so on.
To put it in other words, DevOps embraces the complete culture of agile collaboration where all functions of a company are a part of it.
A team cannot be referred to as a DevOps team when the above values and principles are not complied with.
DevOps is the underlying theme for a lot of lean and agile mental makeup, where opportunities exist for collaboration across an organization.
To put it in a nutshell, DevOps is an initiative to bring to Agile the understanding and approach that software has not been developed until users have been provided with it, and it meets their expectations regarding its performance and rate of change.
Opinions expressed by DZone contributors are their own.