DevOps: What is and Why do we need?

4 min readApr 27, 2022

--

“I am just someone who is interested in this field and plans a career in this target. I’m not an expert, so you may see omissions and errors. Please give me feedback to improve myself.”

Understanding the term DevOps

That the word DevOps gets reduced to technology is a manifesto of how badly we need a cultural shift. -Patrick Debois

Want to learn about DevOps? Everyone has a lot to say about what DevOps is, but let’s first take a look at what it isn’t.

DevOps is not:

→ a name for teams,

→a job title,

→a tool or category name for tools,

→a methodology,

→a software or a specific piece of software,

→a quick fix for an organization’s challenges.

→just Devs and Ops

→ a culture

→everything

So what is DevOps?

The term DevOps is formed from the combination of the words development and operations.

There is no single agreed-upon definition here, so it’s a little harder to understand what it is, but i will try for it.

The Agile Admin says: DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. And DevOps is also characterized by operations staff making use of many of the same techniques as developers for their systems work.

So we can say DevOps is “service lifecycle practices”.

Donovan Brown says: DevOps is the union of people, processes, and products to enable continuous delivery of value to our end users.

So the purpose of these practices is to provide continuous delivery of the value we offer to the end-user. And DevOps practices; brings people, processes, and products together for this purpose.

Now we have a better understanding of what DevOps is and what it isn’t. Now we can learn a little more about this topic. But first, I would like to talk about why we need these practices.

Why do we need DevOps?

Because DevOps; helps to speed up processes, prevent human error, and prevent downtime during updates. Considering how much competition there is today, this would be a pretty good advantage.

Ian Buchanan says: When development and operations teams come together, they reduce lead time, deploy more frequently, and produce higher-quality software.

from https://www.business2community.com/

In the classical software development lifecycle method, software developers, test engineers, and IT professionals take part as 3 different teams. Software developers do the coding, test engineers then test the codes, and the operational team delivers them to customers. The fact that these teams work in isolation from each other and the lack of communication between them causes some problems to occur and slow down the process. Some of those:
→ Test engineers can only test code at the end of the software development process, and a bug that occurs here will prolong the process considerably.
→ Addressing a bug in the value delivered to the end-user will be slower due to a lack of integration and collaboration between teams. In addition, teams will have to spend more time.

Let’s say we are working on an update; After the software developers make the necessary additions, they will send it to be tested, and the operations team will wait for the test to be completed and sent to them to publish this update. Every mistake that occurs in this process will go back to the previous stage and cause the relevant team to work on it again. Isn’t it an annoying process both for the company, the customers, and the employees?

DevOps helps us both in reducing the workload of the employees, in increasing the quality of the product offered, and in accelerating the whole process.

I’m thinking of publishing an article about this whole process. If you’re wondering how it provides all these benefits, the link will be here soon.

Thank you for reading.

DevOps: What is and Why do we need?

Understanding the term DevOps

Why do we need DevOps?

Resources

Written by Ahmet Soğuksu