The history of DevOps: A visual timeline

Powerful DevOps software to build, deploy, and manage security-rich, cloud-native apps across multiple devices, environments, and clouds. Later, in 2008 during an Agile conference held in Toronto, Canada, a man by the name of Andrew Shafer tried to put together a meetup session entitled “Agile Infrastructure.” When Patrick showed up for the session, he was the only one there. Andrew had received so much negative feedback from his posting that not even he showed up to his own session. However, Patrick was so excited to learn of a like-minded person that he hunted him down at the conference and had that talk in the hallway. They formed a discussion group for other people to post their ideas for how to solve this divide between development and operations later that year.

  • Right about now you might be thinking that you’ve just found yourself a new cocktail story, but the history of how DevOps evolved is important for understanding what DevOps is and why it’s important.
  • DevOps had managed to achieve a grassroots following that was starting to put their ideas to use.
  • DevOps is a methodology that helps teams deploy high-quality software through continuous integration and delivery (CI/CD).
  • When put in the context of agile development, the shared accountability and collaboration are the bedrock of having a shared product focus that has a valuable outcome.

If DevOps had a birth certificate, the father’s name would be penned in as Patrick Debois. Patrick was interested in learning IT from every perspective, and in 2007, he began working on a large data center migration where he was in charge of testing. During this project, he realized that the frustrations experienced in projects such as these are from the constant switching back and forth between the development side of the problem and the silo of operations on the other side of the fence. He recognized that a lot of time and effort was wasted navigating the project between these two worlds, but the divide between them seemed too wide to bridge. Most leading cloud computing providers – including AWS, Google, Microsoft Azure, and IBM Cloud – offer some sort of managed DevOps pipeline solution. Find out what’s new on Freepik and get notified about the latest content updates and feature releases.

Why the History of DevOps Matters

The shift to DevOps involves embracing open communication, transparency, and cross-discipline teamwork. The idea behind DevOps is breaking down silos and opening up workspaces for collaboration and discussion. In the pursuit of understanding what something is, it’s often helpful to know where it came from and why it rose to prominence. DevOps engineering can be lucrative, with an average salary of $108,000 per year, according to Glassdoor. Compared to other software engineers, DevOps engineers get paid about the same or slightly higher, except for back-end developers (also called back-end engineers).

Many software engineers use DevOps in their development process or on their team, even if there’s no specific DevOps engineer in their organization. While you might know that DevOps is quite literally a combination of software development (Dev) and IT operations (Ops), what does DevOps mean? DevOps is a methodology that helps teams deploy high-quality software through continuous integration and delivery (CI/CD). Cloud-native is an approach to building applications that leverage foundational cloud computing technologies. The goal of cloud-native is to enable a consistent and optimal application development, deployment, management and performance across public, private and multicloud environments.

DevOps Engineer Definition

If you’re interested in a technical career that requires working closely with people, becoming a DevOps engineer might be right for you. Another way to put this is that DevSecOps is what DevOps was supposed to be from the start. But two of the early significant (and for a time insurmountable) challenges of DevOps adoption were integrating security expertise into cross-functional teams (a cultural problem), and implementing security automation into the DevOps lifecycle (a technical issue). Security came to be perceived as the “Team of ‘No,'” and as an expensive bottleneck in many DevOps practices. At the technical level, DevOps requires a commitment to automation that keeps projects moving within and between workflows, and to feedback and measurement that enable teams to continually accelerate cycles and improve software quality and performance.