What is DevOps | Introduction to DevOps | Intellipaat

hello everyone welcome to this session on what is DevOps today in this session I'll be telling you guys what is DevOps in the briefest manner possible so let's get started now also guys if you have not subscribed to the Intellipaat channel as of now please do that and also click on the notification button if you haven't already to never miss out on any updates from us so now let's get started with what is DevOps well if you have followed the software development evolution you will know that there are three methodologies of software development which are very important the first one being the waterfall model then we have the agile model and then we have the lean model so waterfall model was basically devised basically because we needed a process through which we can develop software right and that was what waterfall model gave us after that we realized that developing software is taking a lot of time it took us years if not months to develop softwares right and this made the customer satisfaction to go really low and hence we needed a new method through which we can deliver software faster and hence we invented the agile method right so agile method solve that problem and we further I treated it and made it even better by using the lean method right so these thing methods were basically used to improve the speed with which we developed software's and that basically solved the problem of customer satisfaction right now this was solved but the question which arises over here is then why did we need DevOps so now let's go ahead and understand what is DevOps exactly well it DevOps aimed at solving a very different problem the problem between the customer and the company was solved DevOps basically focuses on the problem which is within the company now what is the problem within the company so basically the software is developed by a team which is called the tech team or the technical team and the technical team itself has two sub teams which are called the developer team and the operations team now there were problems between these two teams now what was the problem let's go ahead and understand well the work of the developer team was to basically develop software using code right so they used to code that application and then that application was then forwarded to the ops team or the operations team which basically used to upload that particular application onto the server sounds simple right but it isn't that simple now let me tell you some of the problems that were faced for example I'm a developer or you are a developer and you developed an application let's say your system configuration it's I5 CPU and then you have 8gb of RAM you have Windows 10 installed and then you have PHP 5.6 and then you have probably Java somethin Java 7 installed on your system right so this is your system conflict now you develop software and it is running fine on your system now the problem arises when you get the same software for some other person to run let's say you give it to the ops person to run right now the ops person tries the best to have the same environment so let's say he has an AMD processor he has a Windows 10 operating system he has PHP 7 yours was 5.6 his is 7 right he has Java 8 installed so these are the environmental differences which are there between the ops team and your system also it could be that let's say you are developing a software which requires a higher software which is not their only production system or on the testing system again there will be an environment mismatch so what used to happen was when you were able to done or you were done with your software you used to forward it to the ops team the ops team in turn you should send your code back saying it's not running on their system but it's actually not your fault it's not running on their system right they have to check the environment they have to set everything right and only then it will work right but imagine that if there are 50 developers and all of them are developing their own piece of software or they all of them are doing their own piece of work all of them could have their own environments that they're working in right and similarly ops people will have to manage all those 50 environments for all those 50 developers this was basically a very hectic task and the frustration was that the option you should send it back saying you know the code is wrong it's not running on our system please check the code but the developer team it was not their fault also right they did they work their work was finished and this was the problem there was a lot of back and forth between the developer team and the operations team this was the first problem that is the environment mismatch there were few more problems let's discuss those problems as well now let's talk about the second problem the second problem was let's say you as a developer you forwarded your code to the testers right now it will take some time for the testers to basically go through your code find the bugs and send you the report back now you can either wait for that time or you can start off with your next task but the problem is when the bugs come back you have to again leave your work then start off with the first patch of code and against all the bugs against a little testing team wait for the feedback to come back again so it was again a process which was not well structured a lot of back and forth was there so this was again a problem which had to be solved the third problem was that there was no continuous feedback which we were receiving let's say you know there are functional test there is a test that you do through manual testing and you find the bugs in everything right but what happens when the user uses it right when the user uses your software there will be some other kind of bugs which comes up so how do you capture that feedback and incorporate in the developer's work so there was no continuous process for that so these were the problems that had to be solved and these problems were solved using DevOps now if you focus on the word it is a mixture of two words dev and ops right which basically means we had to bridge the gap between the developer team and the operations team and the answer to that was DevOps now let's see how DevOps basically solves us so guys DevOps is not any tool it's not any set of tools it's basically an idea it's a way of thinking as to how software should be developed right so it follows a lifecycle which is basically continuous if you look at the lifecycle of DevOps it basically resembles the infinity sign right it starts off from plan then it moves on to code then we build the software then we test the software then it release the software we deploy the software we monitor the software and then we again come down to planning the software again right this is the lifecycle which is followed in DevOps now how does this solve the problem of what we were facing before the environment mismatch the time taken to give the testing feedback and also the continuous feedback which is not coming back to us from the customers so let's solve the problem number one which is the environment miss fast so there is a tool in the DevOps life cycle which is basically called docker so docker is a basically a very lightweight container system which basically can duplicate environments for you across multiple systems right so that can also be done using a virtual machine if you guys know what a virtual machine is it's basically a yet another operating system which is installed in your host operating system but the problem with the virtual machine is that it takes a lot of space right with docker containers the container can be as small as 50 MB so if you are developing software you develop it inside the docker container and then you just give that container to your ops team and once they run it it will run it as it is as whatever is specified in that container is let's say the container is has around 1 GB of RAM it's following some amd64 architecture it has certain set of software installed on it they will exactly be the same even on the OP sky system so the environment problem was solved then the software problem was solved using automated testing right so instead of asking the testers to test your software is what you used to do was used to connect the lifecycle of the code to your testing lifecycle then where the developer will automatically push the code to github which is basically a place where you upload code it will automatically detect that the code has been uploaded it will push the code on to the testing server where your testing suits are basically placed in and your software will be tested and whatever logs are generally let's say there is a bug which has been identified that will be immediately mailed back to the developer right so like I said we're up DevOps is basically an idea it's basically a way of developing software and you use all these set of tools together in the way of a DevOps lifecycle to basically achieve what we call the DevOps logic lifecycle right so we had docker we had selenium which is basically an automated testing tool the third problem that we had was basically the continous feedback that we needed to receive from a customer's right so whatever customer got whatever bug that had to be immediately reported to the developer so that he can add it in his plan as to what are the things that he has to fix next in the software so this was achieved using software's like nagios it's continuously monitor software's generate logs and whenever there is a log which is it of a bug type or a critical type it is basically mailed to the developer this is a problem that has been faced by a particular customer and this is what needs to be solved right and this is continuously generated and added in a developer's plan now how the DevOps lifecycle achieved over here guys so when you plan let's say what is planned plan is basically when your architect comes in and treads it whatever this is what we have to do that it distributes the work among the developers which is then in turn coded right which is then develope up by the developers which is basically a code stage in DevOps then you have the build stage in the boss which basically resembles the compiling stage where the code is compiled and is basically output in the form of an executable when you achieve that it is then tested on the testing server right when the tester code is tested it is then moved on and it is released onto your github branch which basically is then deployed onto a staging server where you check the final things of the software whether everything is working fine or not nothing is breaking right and when that is achieved it is finally deployed onto the production server right when it is deployed on the production server then the monitoring stage comes in where the software which has been deployed on the production server is continuously monitored and whatever bugs are coming in it is again going back to the plan stage so this is how the infinity sign in devops basically works and this is how basically the whole DevOps lifecycle works alright guys the main thing to focus on here is that no part in the DevOps lifecycle is manual everything is automatic right and that solves the problem of the back-and-forth which is between the developer team and the operations team that is once a developer commits a code on to get up it will automatically be tested if there is any bug it will be immediately mailed back to the developer and he can immediately fix it again try to commit onto github again reputation if everything goes well it will automatically be deployed on to production right obviously there are a lot of stages in between there are a lot of tools which are used in between but yes this session is about what DevOps is and I'm sure this session would have helped you clear doubts about what DevOps is and how is it different from the various other models that you studied while you were basically discussing what software development was now if this session was useful to you guys please like this video and also comment down any queries that you have in regards to this particular video right if you want to learned about in more depth we also happen to have a DevOps tutorial whose link will be there in the description so thanks a lot for listening to me guys have a great day ahead and good bye

Channel: Intellipaat

Views: 9,744

Rating: 4.6932907 out of 5

Keywords: what is devops, introduction to devops, learn devops, devops introduction, devops for beginners, devops course, devops fundamentals, devops concepts, simplilearn devops, what is devops for beginners, devops explained, what is dev ops, devops overview, devops basics, Intellipaat, what is devops easy way, devops tools, what is devops and how it works, devops tutorial for beginners, devops tutorial, devops training, why devops, devops culture, devops intellipaat

Id: 5LZ_Ts9iSNc

Length: 12min 3sec (723 seconds)

Published: Fri Nov 08 2019