# #Day1  Fundamentals of DevOps

### What is DevOps?

"In general, we can say that it is a culture that improves the organization's ability to deliver applications."

In the above, I have said that delivering an application. Not only delivering applications it also ensures automation, quality, continuous monitoring, and continuous testing

Finally, we can say it has

"DevOps is a process of improving the application delivery by ensuring proper automation with maintaining code quality ensuring there is a continuous monitoring and continuous testing in place."

What end goal of a DevOps engineer?

Example:

If the application is delivered in 7 weeks, the main goal of the devops engineer is to speed up the process which is 2 weeks but also ensures automation, quality, continuous monitoring, and continuous testing.

### Why DevOps? -The Benefits

The organizational DevOps transformation has been proven to accelerate the speed, quality and efficiency of software delivery, and improve staff motivation, and morale. It removes silos (the communication obstacles among teams) as well as reliance on a single person or team for the software progression.

Work quality is improved further by using automation software that eliminates boring tasks. By establishing the automated services, the existing operational costs are radically reduced compared to the human equivalent. As the manual work is removed, the staff can focus on the work that increases job satisfaction, and purpose while adding real value to the organization and its customers. The speedier automated processes improve the quality of the release process because steps in the pipeline are standardized, leading to predictable outcomes, reduced cycle times, and higher deployment rates.

### **The before DevOps scenario**

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1694618538089/06eb8d02-9c83-4fa4-875b-d222959692a0.png align="center")

* Software Development team code without knowing how features behave? How do customers feel and how do features address actual needs?
    
* The Quality Assurance team must ensure high-quality standards without having all the tools, and resources required.
    
* The system Engineering team must ship software in production and make sure it runs. If it doesn’t hack into it. a.k.a. Deploy and Pray.
    

### **The after-DevOps scenario**

![](https://cdn.hashnode.com/res/hashnode/image/upload/v1694618945243/0e1b36a7-dddc-4b3f-a683-12bf2e46e598.png align="center")

* Product Teams consisting of Product Managers, UX/UI experts, Software Engineers and others work together (Quality Assurance is not as important as before — it is all pipelined and automated)
    
* Site Reliability Teams become smaller with highly effective tools and technologies in place
    

**Thank you for taking the time to read this blog.**

**I hope you found the information helpful and insightful.**