1 00:00:01,200 --> 00:00:01,590 Hello, folks. 2 00:00:01,690 --> 00:00:02,740 This is Ashish Pandey. 3 00:00:02,850 --> 00:00:07,450 And today we're going to talk about Dakar in the specific and continue in. 4 00:00:08,280 --> 00:00:13,300 We will be talking about the history and a bit of introduction and road Dakar and containers. 5 00:00:14,040 --> 00:00:14,970 Why do we use it? 6 00:00:15,750 --> 00:00:22,280 What is a new Duffett and a bit of what exactly that unable to keep it. 7 00:00:22,830 --> 00:00:23,820 You'll find two things. 8 00:00:24,120 --> 00:00:25,980 One, Dakar as a computer software. 9 00:00:26,070 --> 00:00:30,000 Another Dakar as a company for Docker's, a company that broader DOKO software. 10 00:00:30,960 --> 00:00:37,440 Second distinction we need to know is what exactly is the difference between Dakar and continue right. 11 00:00:37,680 --> 00:00:43,800 So dark the relation between Dakar and continue in the same way that you have Xerox with photocopy the 12 00:00:43,800 --> 00:00:45,780 same religion that you have Google image search. 13 00:00:46,740 --> 00:00:50,080 Okay, so dorkbot is something that popularized the container. 14 00:00:51,240 --> 00:00:53,930 So there are other type of containers as well in the market. 15 00:00:53,970 --> 00:00:57,300 But Docker is the one which is most popular container. 16 00:00:58,840 --> 00:01:07,380 Now Docker Asset is open source software, but it is also a Docker enterprise Edison, which gives basically 17 00:01:07,380 --> 00:01:12,990 a platform to create the container to manage the container and provide enterprise level services to 18 00:01:12,990 --> 00:01:13,980 the other companies. 19 00:01:14,580 --> 00:01:15,870 We'll see more about that later. 20 00:01:17,700 --> 00:01:24,420 So Docker game on in 2013, founded by Sillerman Hikes, and he was also the chief developer. 21 00:01:25,740 --> 00:01:31,680 Now we are going to use all of the slides that Docker itself used to introduce itself to the world. 22 00:01:32,130 --> 00:01:35,200 So this was used by Docker guys in November 2013. 23 00:01:35,790 --> 00:01:36,930 And here's how they introduced. 24 00:01:37,680 --> 00:01:44,310 So they gave it that it took an analogy of the shipping industry with 80 industry, how they have gone 25 00:01:44,310 --> 00:01:52,890 to the same set of problems, for example, in transport industry, in basically international transportation 26 00:01:53,280 --> 00:01:53,850 scenario. 27 00:01:54,930 --> 00:01:58,030 Suppose you have to transport some goods, right? 28 00:01:58,110 --> 00:01:58,470 Good. 29 00:01:58,890 --> 00:02:00,080 Like, it could be food item. 30 00:02:00,090 --> 00:02:01,100 It could be petroleum. 31 00:02:01,110 --> 00:02:03,570 It could be explosives or whatever it is. 32 00:02:04,410 --> 00:02:11,970 Now, the thing is, you need to have a common mechanism to put them on the ship so that they don't 33 00:02:12,180 --> 00:02:13,380 interact with each other. 34 00:02:13,950 --> 00:02:17,310 So you have got this problem, appointive plasty of goods. 35 00:02:17,640 --> 00:02:21,920 And also once it reaches to the cost, then how to transport this. 36 00:02:22,440 --> 00:02:24,690 So one problem is the multiplicity of goods. 37 00:02:25,110 --> 00:02:30,900 And second problem is that once the goods reaches the cost, then how do you transport it? 38 00:02:31,170 --> 00:02:32,640 You can call it the portability issue. 39 00:02:33,300 --> 00:02:35,610 So basically that brings automated from him. 40 00:02:35,970 --> 00:02:40,530 That means you have to transport a lot of goods so that they don't intermixed with each other. 41 00:02:40,980 --> 00:02:43,620 But also, you need to move them around. 42 00:02:44,340 --> 00:02:45,990 So that's a portability issue. 43 00:02:46,020 --> 00:02:48,180 And together they make matters from him. 44 00:02:48,240 --> 00:02:54,860 So the solution that you propose for this problem must be compliant with both the problems. 45 00:02:55,140 --> 00:03:00,210 Whatever solution you are getting, that should solve the intermixing problem as well as the portability 46 00:03:00,210 --> 00:03:00,510 issue. 47 00:03:01,200 --> 00:03:06,870 Now, if you think about the solution, so the solution that came was shipping containers. 48 00:03:07,130 --> 00:03:11,670 Tonight you can put maybe petroleum products in one other container. 49 00:03:11,760 --> 00:03:17,490 And just beside that shipping container, you can put food items in and shipping containers. 50 00:03:17,850 --> 00:03:21,060 It will make sure that they don't intend mixing with each other. 51 00:03:21,600 --> 00:03:26,400 And also, if you think about it, the shipping containers can be moved around pretty easily. 52 00:03:26,580 --> 00:03:34,320 You can use trains or greens or you can use it on the trucks and you can move it around tonight. 53 00:03:34,370 --> 00:03:35,650 Just think about it. 54 00:03:35,670 --> 00:03:38,940 Similar kind of procedures and you have in the industry as well. 55 00:03:39,780 --> 00:03:44,670 So to create an application product, you need multiple technologies. 56 00:03:45,330 --> 00:03:51,420 You need to make sure that these technologies don't in turn mingle with each other, basically. 57 00:03:51,540 --> 00:03:55,300 They don't affect each other in an adverse event. 58 00:03:56,220 --> 00:03:56,510 Right. 59 00:03:56,610 --> 00:04:04,350 And also, once that application gets prepared, then it should be able to run in development in Norman, 60 00:04:04,350 --> 00:04:07,010 in a Cuban woman, in this trading in Norman and so on. 61 00:04:07,680 --> 00:04:10,170 That's basically it's what we call portability. 62 00:04:10,950 --> 00:04:11,280 Right. 63 00:04:11,700 --> 00:04:18,740 Basically, whatever solution you bring out, that should provide some kind of isolation, but that 64 00:04:18,780 --> 00:04:21,300 it should also provide some kind of portability. 65 00:04:21,930 --> 00:04:26,910 And that's where container came to solve this problem in application domain. 66 00:04:27,570 --> 00:04:29,600 We brought something called containment. 67 00:04:30,250 --> 00:04:30,470 Okay. 68 00:04:30,650 --> 00:04:35,160 And doctors and they said, doctor is something that means containerisation very, very easy. 69 00:04:35,400 --> 00:04:36,690 We'll see how going forward. 70 00:04:37,540 --> 00:04:41,250 So now Doc Sudhakar is a shipping container system for the court. 71 00:04:42,030 --> 00:04:45,690 It provides a solution across multiple technologies. 72 00:04:46,050 --> 00:04:53,620 So basically, Docker and prior to the capacity to encapsulate your code into one package. 73 00:04:54,240 --> 00:04:57,000 And then it can be moved around pretty easily. 74 00:04:59,220 --> 00:04:59,670 So. 75 00:04:59,900 --> 00:05:01,580 What is there in it for developers? 76 00:05:02,120 --> 00:05:08,240 Developers can walk in now, portable land time in a moment, which is clean, which is isolated from 77 00:05:08,240 --> 00:05:14,240 others, and they don't have to basically think about the missing dependency packages every time during 78 00:05:14,240 --> 00:05:19,640 the deployment because now they're willing to put everything together in one container and ship the 79 00:05:19,640 --> 00:05:20,660 container itself. 80 00:05:22,760 --> 00:05:28,160 You can run like developers can now run their containers on their own machine. 81 00:05:28,280 --> 00:05:29,780 Containers are very lightweight. 82 00:05:30,920 --> 00:05:36,770 So, in fact, if you think about it, the containers will behave more like a virtual machine. 83 00:05:37,580 --> 00:05:37,760 Okay. 84 00:05:38,230 --> 00:05:42,580 Labor's job machine has its own IP address and its own 49. 85 00:05:42,920 --> 00:05:44,130 Similarly, its container. 86 00:05:44,490 --> 00:05:47,690 So had that one IP address as well as their port. 87 00:05:47,750 --> 00:05:53,720 And it behaves exactly like a standalone VM, but it is very lightweight. 88 00:05:54,230 --> 00:05:56,810 That is a strong, tough container. 89 00:05:56,840 --> 00:06:03,990 So basically it takes a very, very small do this and to launch a container, to kill it and to modify 90 00:06:03,990 --> 00:06:11,110 it so developers can automate testing, integration, packaging, everything. 91 00:06:11,120 --> 00:06:14,630 In fact, anything that you can descript you can automated the containers. 92 00:06:15,860 --> 00:06:16,030 OK. 93 00:06:16,130 --> 00:06:20,770 And this container needs just something called Docker Daemon. 94 00:06:20,780 --> 00:06:21,960 We'll talk about that later. 95 00:06:22,520 --> 00:06:26,970 But basically, it can run on different kind of a platform. 96 00:06:26,990 --> 00:06:30,390 You can then even on tools like Raspberry Pi. 97 00:06:30,860 --> 00:06:35,240 You can you have continuous windows, you content for the next and so on. 98 00:06:36,290 --> 00:06:41,270 So basically in the traditional way, what the work of a little machine was giving you. 99 00:06:41,840 --> 00:06:49,040 Now, most of those things can be provided by the containers, and Docker has made it very, very simplified. 100 00:06:51,950 --> 00:06:53,560 No variety of reasons, guys. 101 00:06:55,240 --> 00:07:03,520 They loved soccer because now if you compare it with managing the teams, managing the containers, 102 00:07:03,550 --> 00:07:05,280 it's very easy, right? 103 00:07:05,560 --> 00:07:13,030 If you think about it just for launching a vean, it might take half an hour or two hours, depending 104 00:07:13,030 --> 00:07:15,130 on what good enough Veum you're talking about. 105 00:07:15,910 --> 00:07:19,240 But running continuous assault are just a matter of seconds. 106 00:07:20,420 --> 00:07:29,950 So not since they can automated, the developers can trade multiple code on this or they will ultimately 107 00:07:29,950 --> 00:07:32,860 idea Christens guys are going to receive good quality of the code. 108 00:07:33,370 --> 00:07:38,370 So this eliminate constant inconsistency between development, production and staging environments. 109 00:07:38,980 --> 00:07:44,720 If the controllers is behaving in one way, in one moment, it will behave exactly same in other enwonwu. 110 00:07:46,000 --> 00:07:53,140 That is one of the strongest argument, in part adopting that the doctor is implemented. 111 00:07:53,710 --> 00:07:59,860 You can segregate the duty of DRDO guys and oxidase your standard of close collaboration. 112 00:08:00,100 --> 00:08:02,950 But you can draw a line that, OK. 113 00:08:03,010 --> 00:08:04,660 This is the right type of developers. 114 00:08:04,690 --> 00:08:05,310 This is the job. 115 00:08:05,800 --> 00:08:06,090 OK. 116 00:08:06,190 --> 00:08:09,900 Of course they need to collaborate, but they can work together in a harmonious way. 117 00:08:11,290 --> 00:08:15,840 So you can you have basically a lot of plug ins with every kind of S.A.C. do it. 118 00:08:15,900 --> 00:08:21,520 For example, if you talk about Dinkin says a C.A.C. detuned, then Jenkins has a docker plug in that 119 00:08:21,520 --> 00:08:26,080 you can use to integrate Dakar with Jenkins. 120 00:08:26,470 --> 00:08:26,810 Okay. 121 00:08:27,340 --> 00:08:34,000 So a lot of C.A.C. tools have got good integration with Docker and a little continuer technologies. 122 00:08:35,180 --> 00:08:40,570 Narcis, the content, as I said, are very lightweight compared to the set of words and VMT. 123 00:08:41,110 --> 00:08:42,610 It saves you a lot of cost. 124 00:08:42,970 --> 00:08:44,830 It saves you lost a lot of time. 125 00:08:45,070 --> 00:08:46,420 It improves the performance. 126 00:08:46,870 --> 00:08:52,780 And you can make this icon of software development pretty fast and pretty activity. 127 00:08:54,760 --> 00:08:57,700 So we talked about segregation of duties in the previous laide. 128 00:08:58,300 --> 00:08:59,200 How to do that. 129 00:08:59,710 --> 00:09:05,500 So this is the golden rule that the developers are going to look inside the continent and oppresses 130 00:09:05,560 --> 00:09:09,990 guys are going to see that how to move those containers looking outside the container. 131 00:09:10,720 --> 00:09:16,660 So Dolapo is going to be responsible for the what for what kind of order to go inside the container? 132 00:09:17,140 --> 00:09:18,850 What would be the dependancy packages? 133 00:09:19,840 --> 00:09:26,530 What would be the ports that I want to be used by internal application and how the data would be consumed. 134 00:09:27,380 --> 00:09:31,960 On the other hand, oppressor's guys are going to talk about that, how to orchestrate these containers, 135 00:09:31,990 --> 00:09:37,120 how to launch the container, how to delete the container, how to give the containers together, how 136 00:09:37,120 --> 00:09:43,810 to make sure that they are accessible from other planes, how to monitor different kind of container 137 00:09:43,810 --> 00:09:46,690 and their performance and how to have never been together. 138 00:09:47,380 --> 00:09:49,170 So that's a part of the idea since, guys. 139 00:09:50,680 --> 00:09:52,210 So how the trade is done. 140 00:09:53,320 --> 00:09:55,180 We'll talk about it in the next video. 141 00:09:56,230 --> 00:09:56,790 See you there.