Chapter 1. Introduction to DevOps and the Internet
DevOps is a term that has many different and varying definitions, but at its core it is simply the creation of a culture within an organization that promotes efficiency and reliability by bridging the gap between development, QA, and operations.
Before going into any detail about how DNS relates to and can be used within a DevOps environment, it is worth taking a short time to reiterate the background and the principles that are at the core of the DevOps movement, and the impact that this movement has had on companies that have implemented it.
Background
Traditionally, software was built by one group of people, development, tested by another group, QA, and maintained by a third group, operations. Each of these groups was siloed and focused on different deliverables. Development focused on writing code to implement functionality, QA focused on ensuring there were no issues with the code, and operations focused on ensuring that platforms remained available.
The result was that the progression of functionality to production was often slow, and typically only a small number of large deploys per year were made. The division in responsibility often led to finger-pointing when problems arose.
Through the early 2000s, the Agile development movement made great strides forward in improving the process by which software was developed. The movement broke down barriers between business users, business analysts, development, and QA to develop ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access