It Is Time to Correct the Nine Misunderstandings about DevOps！ - Weekly Sharing

Summary : Although most organizations have successfully deployed DevOps to achieve the necessary goals and objectives, DevOps still have some misunderstandings. This article will mainly focus on the correction of these misunderstandings.

DevOps is a combination of development, operation and maintenance. It helps to integrate and automate the test process and deploy the repository. It also provides transparency and flexibility. DevOps aims to :

Faster Time to Market (TTM)
Reduce lead time between fixes
Increase deployment frequency
Faster recovery time
Reduce the failure rate of the new version

Many business sector leaders know that faster marketing is a survival skill, not just a goal. Managers, especially those in the IT industry, have felt the pressure to execute processes faster and more effectively and make better business decisions. Although most organizations have successfully deployed DevOps to achieve the necessary goals and objectives, DevOps still have some misunderstandings. Here are some corrections to misunderstandings.

1. DevOps Is Not a Set of Automation Tools

DevOps is a different way of thinking about deploying and monitoring applications rather than a set of automation tools that can be purchased. Collaboration, continuous delivery, continuous testing, and continuous integration are not implementation tools. Instead, they are practices that need to be adopted in the project. Although many tools, such as ZenTao, Git Hub, and Docker, usually contribute to the implementation of DevOps, they are effective only when team members know how to optimize and introduce them into their working methods.

2. Not Every Project Program Has to Change

The concept of redesigning programs for every new project runs counter to implementing DevOps. Having a single set of processes that can be easily modified as needed and applied to various projects leaves room for predictability. In this approach, everyone is familiar with their job role and needs to operate the process.

DevOps practices need to be adaptable and flexible to implement them into server configuration, exception testing, deployment cycles, and empowering development teams. This is only possible if the team thoroughly understands the entire process through repetition.

3. DevOps Not Just for Small Companies or Start-ups

Leading organizations including Netflix, NASA, Amazon, Google, Starbucks, LinkedIn, GE, Target, Airbnb, HubSpot, Nike, and others are practicing DevOps. It is developed and used for everyone and does not limit the size of the industry and the company. Each business wants to make the desired improvements during its cycle or market time.DevOps can help companies increase their market time regularly and make huge returns. That's why most companies implement this approach. The CEO of Intellipaat, an e-learning institution, says his DevOps certification program services large companies ranging from small to different sizes.

4. DevOps Is Not a Substitute for Agile

Unlike most ideas, DevOps does not replace agile, which we can see as a continuation or agile activator. Continuous deployment, continuous integration, and continuous delivery pipeline of continuous delivery can be realized with the help of DevOps.Furthermore, it allows for calculating the potentially deliverable code at the end of each iteration. Thus, the DevOps and Agile collaboration provides the best results and experience.

5. DevOps Did Not Cancel IT Operation and Maintenance

According to the concept of NoOps, the IT industry will become very automated and do not need any internal team to manage software. In addition, it is believed that microservices will make DevOps operations obsolete. However, operation and maintenance are always needed, no matter how automated the service becomes. Although there may be some changes in these operations, they still have importance in DevOps.

6. DevOps Is Not Developed for Open Source Software

Typically, DevOps is implemented in organizations using the LAMP (Linux, Apache, MySQL, and PHP) stack, as well as with various open-source tools (such as Jenkins, Docker, Ansible, Git, Chef, ELK, Nexus, Sonar, Zentao, Nagios, and Gerrit). However, obtaining a successful DevOps result does not depend on the technique used. Many organizations use COBOL, Microsoft.NET, mainframe assembler code, SAP, and embedded systems.

7. The DevOps Can Be Compatible with ITIL

ITIL represents the Information Technology Infrastructure Library. It consists of detailed practices in IT Service Management (ITSM), designed to align the various IT services with their individual business needs. DevOps is compatible with ITIL, but the ITIL processes are fully automated to support the high deployment frequency and short delivery times associated with DevOps. This addresses many issues associated with the configuration and release management process.

8. DevOps Is Not Equivalent to Continuous Delivery

Although the continuous delivery of software shows that enterprises have implemented important components of DevOps, it is not a binary relationship. These two services are not identical. They are definitely different.

The main focus of DevOps should be to improve the work culture and maintain the infrastructure and software. In addition, it must support the sales and marketing departments.

9. DevOps Can Also Run When It Leaves the Cloud

Most people call DevOps cloud. The cloud provides dynamic infrastructure resources for testers and developers to quickly obtain the test environment, rather than waiting for the request to be completed manually. However, this does not mean that a cloud for DevOps is required. This software can also be used if there is an efficient process to obtain resources that can be deployed and tested for changes in the application.

If you want to know more about DevOps, please check out more articles:

1. 7 Kanban Cadences

2. DevOps life cycle, all you want to know is here !

3. DevOps Knowledge Points - 3C

4. Should Developers Be Afraid of Low Code?

5. What Are The Complete Scrum Artifacts?

6. A Brief History of Agile: Jeff Sutherland——Doing Twice the Work in Half the Time