Patrick Debois coined the term “DevOps” in 2009. He is a Belgian consultant, agile practitioner and project manager, who became one of the early leaders of DevOps and formed this word by combining “Dev” as in development, and “Ops” as in operations.
In this case, “Dev” does not refer only to developers, but to all people involved in the development of a software product from disciplines such as Q&A, development, testing, planning, etc.
Similarly, “Ops” is an umbrella term for everyone involved in the operations team, including systems engineers, database administrators , system administrators, security experts, network engineers, release engineers, and operations staff, among others.
As explained in the previous section, DevOps is a mindset or culture. And this mindset is not something that has been carved in a single stone.
On the contrary, it originated in the best minds years ago and was nurtured bosnia and herzegovina phone number dataand conceptualized by forward-thinking experts from various IT disciplines.
Many core ideas of DevOps are inspired by practices such as Lean, Agile, enterprise systems management, The Toyota Way, and Deming's Plan-Do-Check-Act method.
In 1993, the Telecommunications Information Networking Architecture Consortium defined a service lifecycle model. This model combined telecommunications operations with software development.
Some practitioners claim that DevOps emerged slowly as a method that opposed the prescriptive “top-down” approach of ITIL . Instead, DevOps favored a “bottom-up” approach and gained adherents, providing a flexible software development practice rather than a rigid framework .
In 2009, the first ever DevOps-based conference, Devopsdays, was held in Belgium. Patrick Debois laid the groundwork for this conference, which spread as a movement to other parts of the world.
Let's analyze the two main methods preceding DevOps:
The Origin of DevOps
-
mouakter13
- Posts: 176
- Joined: Mon Dec 23, 2024 4:06 am