DevOps

Technically it has many definitions over the web Amazon has one kind of definition, and Azure has a different meaning, likewise, they defined it as their workflow.

In simple words, DevOps is a culture or a practice that would increase your organization's ability to deliver the application quickly.

Let us take an example there is an organization called XYZ, let us assume there is a new feature or a new version is going to release. When they want to release that particular version to production(end-user), they may take 10 days or 1 month to give it to the end-user and while happening that process, there will be cases to stop the existing version hence users cannot use that application. This may cause loss to the organization and team.

So, to overcome this kind of problem DevOps came into the picture.

Is DevOps only for 'delivery'? No, there were some other things which include in DevOps,

• Automation

• Quality

• Monitoring

• Testing

We will discuss those topics later.

Now the new definition, DevOps is the process of improving delivery(i.e, making delivery quicker) by ensuring that there is proper automation, quality of code, continuous monitoring, and continuous testing.

The main goal of DevOps is that reduces manual tasks and fasten the process of delivery.

Why DevOps came into the picture?

Previously the organization's process would be like this,

Here, what the organization should do? They should deliver their product to the customer/end-user.To make that happen, there will be some internal workflow.

Let us consider an example of XYZ company, in that company their task is to make a web page of their own. So, there will be the involvement of some engineers.

If we look at the above image which describes the workflow, In that firstly 'Developers' design the web page and implement it by writing code. Let us assume developers have written all the code and it is ready to test, but before testing by other members of that company, those persons should have access to that code. So, that code is in centralized locations like GitHub, GitLab, and bitbucket, we will discuss this in later sections.

Now the code has centralized which means company members can access them. Here comes the main task to run the application on different servers to check whether that application is running properly or not. To make this happen, within the company there will be a role called "System Admin" who takes care of creating Servers, and VMs(Virtual Machines) to test/run that application.

When the app is running on some VM there should be a person who tests that app, here one more role comes into the picture "Tester", this guy tests the application and gives feedback to developers about that app.

When everything is set which means code is developed, all tests are passed and there is the only thing left is releasing that application so that users/customers can use it. Here comes another special role "BRE(Build and Release Engineer)", he takes the app to production and releases that application.

Here if we observe, there involvement of three specific roles to make the application from development to production

• SysAdmin

• Tester

• BRE

The whole process may take at least a minimum of 2 to 3 months to happen the total process, which is time taking process.

To overcome this manual process DevOps came into the picture, by Automating the process of creating VMs, checking the quality of code written by developers, testing the supplied application, and continuously monitoring the status of the application. This is the reason DevOps came into the picture.