1 00:00:00,480 --> 00:00:03,480 foreign 2 00:00:09,430 --> 00:00:12,510 [Music] 3 00:00:13,940 --> 00:00:18,119 he's going to be talking to us about the 4 00:00:16,199 --> 00:00:19,560 power of edge Computing and why it 5 00:00:18,119 --> 00:00:21,050 really matters 6 00:00:19,560 --> 00:00:27,000 please make them feel welcome 7 00:00:21,050 --> 00:00:29,160 [Applause] 8 00:00:27,000 --> 00:00:31,019 hello everybody thank you for being here 9 00:00:29,160 --> 00:00:32,940 I know there are many amazing talks 10 00:00:31,019 --> 00:00:35,219 going on in other halls and you all 11 00:00:32,940 --> 00:00:36,960 being here means a lot to me so today 12 00:00:35,219 --> 00:00:38,940 I'm going to talk about Edge Computing 13 00:00:36,960 --> 00:00:41,520 so how how many of you know what Edge 14 00:00:38,940 --> 00:00:43,980 Computing is 15 00:00:41,520 --> 00:00:46,680 okay a few so I hope the number goes 16 00:00:43,980 --> 00:00:48,960 Higher by the end of this talk so here's 17 00:00:46,680 --> 00:00:51,059 a little context about myself I am 18 00:00:48,960 --> 00:00:53,579 swastika and I work as a developer 19 00:00:51,059 --> 00:00:56,520 Advocate at nanjayo it's a backend as 20 00:00:53,579 --> 00:00:58,440 service built on top of kubernetes and 21 00:00:56,520 --> 00:01:00,719 previously I was working as a developer 22 00:00:58,440 --> 00:01:04,019 Advocate at torso database which is an 23 00:01:00,719 --> 00:01:07,020 edge database so that's how I got into 24 00:01:04,019 --> 00:01:09,180 Edge database I also create educational 25 00:01:07,020 --> 00:01:11,400 content on platforms like Twitter and 26 00:01:09,180 --> 00:01:13,200 Linkedin and hopefully by the end of 27 00:01:11,400 --> 00:01:15,900 this year I'll be adding a public 28 00:01:13,200 --> 00:01:18,540 speaker to my introduction 29 00:01:15,900 --> 00:01:20,159 so this is how the agenda looks for for 30 00:01:18,540 --> 00:01:22,439 the talks we'll be seeing what is Edge 31 00:01:20,159 --> 00:01:24,900 Computing how it is different from cloud 32 00:01:22,439 --> 00:01:27,360 computing what are the use cases of edge 33 00:01:24,900 --> 00:01:30,119 Computing and uh how one should decide 34 00:01:27,360 --> 00:01:33,200 if if they should go with Edge Computing 35 00:01:30,119 --> 00:01:33,200 or cloud computing 36 00:01:34,920 --> 00:01:39,960 so a lot of my friends who have been to 37 00:01:37,079 --> 00:01:42,420 the US always shared how fast the web 38 00:01:39,960 --> 00:01:43,860 experience is has come in the US as 39 00:01:42,420 --> 00:01:46,200 compared to the other parts of the world 40 00:01:43,860 --> 00:01:48,240 and I majorly thought it's because of 41 00:01:46,200 --> 00:01:50,579 the high-speed internet or maybe they 42 00:01:48,240 --> 00:01:54,060 have a better technology but what what 43 00:01:50,579 --> 00:01:56,640 does actually happens when if we need a 44 00:01:54,060 --> 00:01:59,040 great web experience so for example if 45 00:01:56,640 --> 00:02:00,780 we click on a particular link uh user 46 00:01:59,040 --> 00:02:02,700 sends the request to the server the 47 00:02:00,780 --> 00:02:04,920 server responses and transmitted the 48 00:02:02,700 --> 00:02:07,860 necessary data and sends the request 49 00:02:04,920 --> 00:02:10,319 back to the user and the time taken in 50 00:02:07,860 --> 00:02:13,319 this process is basically depends on 51 00:02:10,319 --> 00:02:16,200 three things the speed of your internet 52 00:02:13,319 --> 00:02:19,140 processing time at the user's end and 53 00:02:16,200 --> 00:02:23,180 the cloud centers and and the most 54 00:02:19,140 --> 00:02:23,180 important thing is the time taken 55 00:02:28,800 --> 00:02:32,879 and the most 56 00:02:30,420 --> 00:02:35,459 and the most important thing is the time 57 00:02:32,879 --> 00:02:38,520 taken by the data to travel from cloud 58 00:02:35,459 --> 00:02:41,040 Center to the user and back and forth so 59 00:02:38,520 --> 00:02:43,440 uh because most of the data centers are 60 00:02:41,040 --> 00:02:46,080 anywhere placed in the US so the speed 61 00:02:43,440 --> 00:02:48,239 and the web experience is way better in 62 00:02:46,080 --> 00:02:50,700 the US as compared to the other parts of 63 00:02:48,239 --> 00:02:54,180 the world so Edge Computing is one 64 00:02:50,700 --> 00:02:56,780 technology which can help people to have 65 00:02:54,180 --> 00:02:59,940 similar experience with web web 66 00:02:56,780 --> 00:03:02,099 interaction when if even if they are in 67 00:02:59,940 --> 00:03:05,040 any part of the world 68 00:03:02,099 --> 00:03:06,720 so Edge Computing is kind of similar to 69 00:03:05,040 --> 00:03:09,420 cloud computing with one major 70 00:03:06,720 --> 00:03:11,959 difference that is centralization so in 71 00:03:09,420 --> 00:03:14,580 in the case of cloud computing we take 72 00:03:11,959 --> 00:03:16,860 Computing to the cloud centers while in 73 00:03:14,580 --> 00:03:19,860 the case of edge Computing we take cloud 74 00:03:16,860 --> 00:03:22,920 cloud centers closer to the data where 75 00:03:19,860 --> 00:03:25,800 where the user has created the data so 76 00:03:22,920 --> 00:03:28,920 we'll see which will directly decrease 77 00:03:25,800 --> 00:03:30,599 the latency so here uh here are the two 78 00:03:28,920 --> 00:03:33,680 tools which can show what is the 79 00:03:30,599 --> 00:03:33,680 difference in the latency 80 00:03:36,780 --> 00:03:38,780 um 81 00:03:43,319 --> 00:03:48,599 so this this is a tool by virtual where 82 00:03:46,620 --> 00:03:49,980 you can 83 00:03:48,599 --> 00:03:52,620 come on 84 00:03:49,980 --> 00:03:55,940 how do I click on it 85 00:03:52,620 --> 00:03:55,940 how do I click on it 86 00:04:00,900 --> 00:04:03,260 no 87 00:04:05,760 --> 00:04:08,720 third okay 88 00:04:09,120 --> 00:04:14,060 so if we just choose a data service here 89 00:04:26,340 --> 00:04:32,160 so the Blue Line shows the traditional 90 00:04:28,440 --> 00:04:34,259 cloud computing latency when the data is 91 00:04:32,160 --> 00:04:36,419 directly taken through through the us 92 00:04:34,259 --> 00:04:38,220 while the purple line shows the edge 93 00:04:36,419 --> 00:04:40,380 Computing functions when the data is 94 00:04:38,220 --> 00:04:42,479 processed at the edge com Edge Network 95 00:04:40,380 --> 00:04:47,060 so you can see there's a huge difference 96 00:04:42,479 --> 00:04:47,060 in blue and the purple lines and 97 00:04:53,460 --> 00:04:56,840 it's not touching that 98 00:04:56,880 --> 00:05:00,919 you will go back to the other window 99 00:04:58,380 --> 00:05:00,919 yeah 100 00:05:01,380 --> 00:05:03,560 foreign 101 00:05:09,060 --> 00:05:14,340 so here's an example of latency 102 00:05:11,520 --> 00:05:16,380 difference between the USA and India so 103 00:05:14,340 --> 00:05:18,600 on the right hand side we have the 104 00:05:16,380 --> 00:05:20,280 latency distribution in the US you would 105 00:05:18,600 --> 00:05:21,600 see there's not much of a difference in 106 00:05:20,280 --> 00:05:23,460 the blue and the purple line on the 107 00:05:21,600 --> 00:05:25,560 right hand side because even if we take 108 00:05:23,460 --> 00:05:27,539 the example of cloud computing the data 109 00:05:25,560 --> 00:05:28,979 center are present there only so it 110 00:05:27,539 --> 00:05:30,840 doesn't make much of a difference in the 111 00:05:28,979 --> 00:05:33,539 latency while on the left hand side 112 00:05:30,840 --> 00:05:37,380 you'll see the latency distribution in 113 00:05:33,539 --> 00:05:39,060 India is way different and the there's a 114 00:05:37,380 --> 00:05:40,919 huge difference between purple line and 115 00:05:39,060 --> 00:05:42,419 the blue line because the blue lines is 116 00:05:40,919 --> 00:05:44,940 showing the data which is transmitted 117 00:05:42,419 --> 00:05:46,560 through the us while the purple lines is 118 00:05:44,940 --> 00:05:48,240 processing the data through Edge 119 00:05:46,560 --> 00:05:50,940 Computing when the data servers are 120 00:05:48,240 --> 00:05:53,160 present at the place where the data has 121 00:05:50,940 --> 00:05:56,960 been created 122 00:05:53,160 --> 00:05:56,960 so now we have another tool 123 00:06:23,880 --> 00:06:28,280 s 124 00:06:25,740 --> 00:06:28,280 yeah 125 00:06:28,680 --> 00:06:33,120 so if we switch it off this is a tool by 126 00:06:30,840 --> 00:06:34,979 torso database if we switch it off we 127 00:06:33,120 --> 00:06:37,319 can see the data centers are present in 128 00:06:34,979 --> 00:06:40,199 the New Jersey and the latency is way 129 00:06:37,319 --> 00:06:42,960 way lower than any part of the world as 130 00:06:40,199 --> 00:06:45,800 compared to the US uh and if you switch 131 00:06:42,960 --> 00:06:45,800 it back 132 00:06:46,020 --> 00:06:50,340 so now we see there are multiple data 133 00:06:48,180 --> 00:06:53,460 centers present which are like replica 134 00:06:50,340 --> 00:06:55,380 of data centers uh created locally where 135 00:06:53,460 --> 00:06:57,060 the data has been created so you can see 136 00:06:55,380 --> 00:06:59,039 there's a huge difference in the latency 137 00:06:57,060 --> 00:07:01,259 in the other parts of the world as well 138 00:06:59,039 --> 00:07:03,919 as compared to the one in the cloud 139 00:07:01,259 --> 00:07:03,919 computing 140 00:07:16,620 --> 00:07:21,419 so the key components of Edge Edge 141 00:07:19,259 --> 00:07:23,340 infrastructure so in Edge infrastructure 142 00:07:21,419 --> 00:07:25,620 there are basically two main components 143 00:07:23,340 --> 00:07:28,199 one is Edge devices and other is Edge 144 00:07:25,620 --> 00:07:30,720 data centers Edge devices you can think 145 00:07:28,199 --> 00:07:32,639 of them as a hardware which manages the 146 00:07:30,720 --> 00:07:35,460 flow between the server side and the 147 00:07:32,639 --> 00:07:37,680 users so it's it manages the boundary 148 00:07:35,460 --> 00:07:40,380 between the networks 149 00:07:37,680 --> 00:07:42,539 um so for examples iot sensors smart 150 00:07:40,380 --> 00:07:44,940 cameras or processors are few of the 151 00:07:42,539 --> 00:07:46,800 edge devices while the edge data centers 152 00:07:44,940 --> 00:07:49,560 are the smaller data centers which are 153 00:07:46,800 --> 00:07:53,220 created near to the users where the data 154 00:07:49,560 --> 00:07:55,500 has to be created and it acts as uh it 155 00:07:53,220 --> 00:07:58,139 delivers cloud computing resources to 156 00:07:55,500 --> 00:08:00,900 Edge devices 157 00:07:58,139 --> 00:08:03,000 here's an example of how Edge Computing 158 00:08:00,900 --> 00:08:05,940 Works in in 159 00:08:03,000 --> 00:08:09,479 in iot systems so here we have some Edge 160 00:08:05,940 --> 00:08:11,340 devices data is transmitted to the edge 161 00:08:09,479 --> 00:08:13,680 Network and all the processing of the 162 00:08:11,340 --> 00:08:17,580 data has done has to be done here only 163 00:08:13,680 --> 00:08:20,340 while only the results of this data has 164 00:08:17,580 --> 00:08:22,259 to be sent to the data centers for 165 00:08:20,340 --> 00:08:25,080 further evaluation and human interaction 166 00:08:22,259 --> 00:08:27,840 rest of the data is already been 167 00:08:25,080 --> 00:08:30,120 processed which which also helps apart 168 00:08:27,840 --> 00:08:32,820 from reducing the latency it also helps 169 00:08:30,120 --> 00:08:35,039 in high security because if you have a 170 00:08:32,820 --> 00:08:37,260 sensitive data you can process it at the 171 00:08:35,039 --> 00:08:41,700 network Edge only and the result of the 172 00:08:37,260 --> 00:08:43,380 data can only the document or the data 173 00:08:41,700 --> 00:08:45,000 which is not that much sensitive can be 174 00:08:43,380 --> 00:08:47,580 anonymized can be sent to the cloud 175 00:08:45,000 --> 00:08:51,019 centers and rest can be processed here 176 00:08:47,580 --> 00:08:51,019 and sent back from here only 177 00:08:51,480 --> 00:08:56,700 so cloud cloud computing versus uh 178 00:08:54,839 --> 00:08:58,320 Edge Computing so there are four 179 00:08:56,700 --> 00:08:59,940 scenarios on the basis of which we'll 180 00:08:58,320 --> 00:09:02,000 see how what is the difference between 181 00:08:59,940 --> 00:09:04,620 Edge Computing and cloud computing 182 00:09:02,000 --> 00:09:06,240 centralization so this is the major 183 00:09:04,620 --> 00:09:08,700 difference between Edge Computing and 184 00:09:06,240 --> 00:09:11,160 cloud computing in cloud computing we 185 00:09:08,700 --> 00:09:13,320 take the data to the cloud centers and 186 00:09:11,160 --> 00:09:15,000 the data centers present at just one 187 00:09:13,320 --> 00:09:16,620 location while in the case of edge 188 00:09:15,000 --> 00:09:19,620 Computing there are multiple data 189 00:09:16,620 --> 00:09:20,820 centers created around the world data 190 00:09:19,620 --> 00:09:23,339 distribution 191 00:09:20,820 --> 00:09:25,320 um in cloud computing since the data 192 00:09:23,339 --> 00:09:27,360 center is present at just one place all 193 00:09:25,320 --> 00:09:29,820 the data is there's no distribution of 194 00:09:27,360 --> 00:09:32,160 the data all the data is stored managed 195 00:09:29,820 --> 00:09:34,500 processed at just one place while in the 196 00:09:32,160 --> 00:09:36,180 case of edge Computing the data is 197 00:09:34,500 --> 00:09:39,839 distributed between multiple data 198 00:09:36,180 --> 00:09:43,080 centers and maybe some part of the data 199 00:09:39,839 --> 00:09:45,660 is also sent to the leading data centers 200 00:09:43,080 --> 00:09:48,360 data processing 201 00:09:45,660 --> 00:09:51,060 so Edge Computing is way faster in the 202 00:09:48,360 --> 00:09:53,100 Pro in data processing as compared to 203 00:09:51,060 --> 00:09:55,140 cloud computing since the data is 204 00:09:53,100 --> 00:09:58,260 processed very near to the where it is 205 00:09:55,140 --> 00:10:01,860 created so it it reduces the latency it 206 00:09:58,260 --> 00:10:04,260 increases the security and helps in 207 00:10:01,860 --> 00:10:05,760 providing a action driven solution in 208 00:10:04,260 --> 00:10:07,920 real time 209 00:10:05,760 --> 00:10:09,899 as compared to cloud computing the data 210 00:10:07,920 --> 00:10:11,880 has be has to be processed at just one 211 00:10:09,899 --> 00:10:13,800 place and it doesn't matter how far it 212 00:10:11,880 --> 00:10:16,560 is from from other places of the world 213 00:10:13,800 --> 00:10:19,440 it it's gonna take time uh real-time 214 00:10:16,560 --> 00:10:21,720 interaction so the cloud computing and 215 00:10:19,440 --> 00:10:23,220 Edge Computing both follows real-time 216 00:10:21,720 --> 00:10:26,220 interaction but in the case of cloud 217 00:10:23,220 --> 00:10:27,839 computing uh it's not always possible to 218 00:10:26,220 --> 00:10:30,000 have real-time interaction because of 219 00:10:27,839 --> 00:10:31,860 the delay and the latencies while in the 220 00:10:30,000 --> 00:10:34,620 edge Computing the chances of delay and 221 00:10:31,860 --> 00:10:37,019 the latencies is way lower than it's 222 00:10:34,620 --> 00:10:39,779 cloud computing 223 00:10:37,019 --> 00:10:41,279 use cases of cloud computing so as I 224 00:10:39,779 --> 00:10:43,440 mentioned there are the three main 225 00:10:41,279 --> 00:10:46,079 benefits of cloud Edge Computing are low 226 00:10:43,440 --> 00:10:49,019 latency real-time data interaction and 227 00:10:46,079 --> 00:10:51,180 high security for for sensitive data so 228 00:10:49,019 --> 00:10:53,040 when we talk about low latencies uh 229 00:10:51,180 --> 00:10:56,160 everyone deserves low latencies and 230 00:10:53,040 --> 00:10:58,260 anyone and every in any part of the 231 00:10:56,160 --> 00:11:00,660 world is of slow latency so they can 232 00:10:58,260 --> 00:11:03,300 achieve that latency with Edge Computing 233 00:11:00,660 --> 00:11:05,880 way easily if they have data local data 234 00:11:03,300 --> 00:11:08,100 centers near to the place uh while in 235 00:11:05,880 --> 00:11:11,040 the case of cloud computing the data 236 00:11:08,100 --> 00:11:12,959 data has to go to the data center in in 237 00:11:11,040 --> 00:11:15,660 present most of the data scientists 238 00:11:12,959 --> 00:11:17,700 present in the US only real-time data 239 00:11:15,660 --> 00:11:20,700 processing so in devices like iot 240 00:11:17,700 --> 00:11:23,519 systems or autonomous vehicles uh there 241 00:11:20,700 --> 00:11:26,100 are like hundreds of different uh Edge 242 00:11:23,519 --> 00:11:28,800 devices which require to process data 243 00:11:26,100 --> 00:11:30,839 and the the massive amount of data has 244 00:11:28,800 --> 00:11:33,839 to be sent to the Cloud Server then it 245 00:11:30,839 --> 00:11:35,940 is sent back to the edge devices which 246 00:11:33,839 --> 00:11:37,680 is a time taking process so in the case 247 00:11:35,940 --> 00:11:40,140 of edge Computing that they data is 248 00:11:37,680 --> 00:11:42,300 processed at the place of edge data 249 00:11:40,140 --> 00:11:44,880 servers which is very near to the place 250 00:11:42,300 --> 00:11:47,700 where the data has been generated so it 251 00:11:44,880 --> 00:11:50,339 also helps in increasing in it increases 252 00:11:47,700 --> 00:11:53,880 the speed at which the solution can be 253 00:11:50,339 --> 00:11:57,300 provided or a response can be created 254 00:11:53,880 --> 00:11:59,820 for data privacy again sensitive data 255 00:11:57,300 --> 00:12:02,399 can be processed and analyzed locally at 256 00:11:59,820 --> 00:12:05,579 the data centers replica of data centers 257 00:12:02,399 --> 00:12:07,560 present near to the users uh and while 258 00:12:05,579 --> 00:12:09,839 the anonymized data can be sent to the 259 00:12:07,560 --> 00:12:12,600 cloud uh which does which does not 260 00:12:09,839 --> 00:12:15,899 contain that much sensitive data and so 261 00:12:12,600 --> 00:12:21,260 the sensitive data can be processed from 262 00:12:15,899 --> 00:12:21,260 from uh from the local data centers only 263 00:12:22,680 --> 00:12:27,660 so to decide between Edge Computing and 264 00:12:25,380 --> 00:12:29,700 cloud computing it's it's not something 265 00:12:27,660 --> 00:12:31,740 like they are not an interchangeable 266 00:12:29,700 --> 00:12:34,200 Technologies both have different 267 00:12:31,740 --> 00:12:37,019 purposes and we we need to decide on the 268 00:12:34,200 --> 00:12:38,519 on the basis of what kind of product we 269 00:12:37,019 --> 00:12:40,260 are looking for what are our 270 00:12:38,519 --> 00:12:42,000 requirements what's going to be our need 271 00:12:40,260 --> 00:12:43,740 in the next few years 272 00:12:42,000 --> 00:12:46,380 so for considerations for cloud 273 00:12:43,740 --> 00:12:49,440 computing so there are three main 274 00:12:46,380 --> 00:12:51,959 considerations that is data volume data 275 00:12:49,440 --> 00:12:54,420 sensitivity and latency requirement so 276 00:12:51,959 --> 00:12:56,040 if if the data volume is huge so it it 277 00:12:54,420 --> 00:12:58,860 would be difficult for small data 278 00:12:56,040 --> 00:13:01,019 centers created near the users to 279 00:12:58,860 --> 00:13:03,839 process that much data and send it back 280 00:13:01,019 --> 00:13:05,459 to the users so in cases of uh maybe 281 00:13:03,839 --> 00:13:07,920 like a healthcare system or financial 282 00:13:05,459 --> 00:13:09,959 system where a huge amount of data is 283 00:13:07,920 --> 00:13:12,060 created every day cloud computing would 284 00:13:09,959 --> 00:13:14,339 be a better option because uh even if it 285 00:13:12,060 --> 00:13:16,980 is slower but the data from complexities 286 00:13:14,339 --> 00:13:19,740 and solutions would be more reliable as 287 00:13:16,980 --> 00:13:21,959 compared to Edge computing second data 288 00:13:19,740 --> 00:13:24,540 sensitivity if you have a sensitive data 289 00:13:21,959 --> 00:13:26,459 where data breach can be a problem in 290 00:13:24,540 --> 00:13:29,339 that case cloud computing is a better 291 00:13:26,459 --> 00:13:31,980 option because it anyways you can 292 00:13:29,339 --> 00:13:34,620 process it locally you don't do not need 293 00:13:31,980 --> 00:13:35,839 to send it to the cloud servers so you 294 00:13:34,620 --> 00:13:39,360 can say 295 00:13:35,839 --> 00:13:42,480 save the part where you need the main 296 00:13:39,360 --> 00:13:45,660 data latency requirement again Edge 297 00:13:42,480 --> 00:13:47,880 Computing decreases the latency by a 298 00:13:45,660 --> 00:13:51,420 huge number so if you need a fast 299 00:13:47,880 --> 00:13:53,820 response a faster web experience Edge 300 00:13:51,420 --> 00:13:56,339 Computing could be the go to choice 301 00:13:53,820 --> 00:13:58,440 for cloud computing scalability and 302 00:13:56,339 --> 00:14:00,540 intensive tasks so as of now cloud 303 00:13:58,440 --> 00:14:02,519 computing has been in the industry for a 304 00:14:00,540 --> 00:14:04,740 longer period of time so it 305 00:14:02,519 --> 00:14:06,720 automatically have has much more 306 00:14:04,740 --> 00:14:09,000 platforms or products people are more 307 00:14:06,720 --> 00:14:11,180 use people are using it more as compared 308 00:14:09,000 --> 00:14:13,980 to Edge Computing there are many more 309 00:14:11,180 --> 00:14:15,899 products which on which you can build 310 00:14:13,980 --> 00:14:18,779 using cloud computing as compared to 311 00:14:15,899 --> 00:14:21,959 Edge Computing so 312 00:14:18,779 --> 00:14:24,120 anyway it it's gonna be it's easier to 313 00:14:21,959 --> 00:14:26,880 rely on on just rent a cloud service 314 00:14:24,120 --> 00:14:29,639 provider as compared to Edge Computing 315 00:14:26,880 --> 00:14:32,040 uh for the higher intensive tasks where 316 00:14:29,639 --> 00:14:34,200 there's a lot of computational uh 317 00:14:32,040 --> 00:14:36,000 processing required of Big Data analysis 318 00:14:34,200 --> 00:14:39,300 is required so again that is difficult 319 00:14:36,000 --> 00:14:41,579 for smaller data centers to process that 320 00:14:39,300 --> 00:14:45,180 much data and while in the case of cloud 321 00:14:41,579 --> 00:14:48,000 computing they have bigger data centers 322 00:14:45,180 --> 00:14:51,060 where high level of computations and 323 00:14:48,000 --> 00:14:53,579 data analysis can be done hybrid 324 00:14:51,060 --> 00:14:55,380 solution so as of now we do not have a 325 00:14:53,579 --> 00:14:57,899 solution where we can have a mix of 326 00:14:55,380 --> 00:14:59,459 cloud computing and Edge Computing but 327 00:14:57,899 --> 00:15:01,620 there are few companies who are working 328 00:14:59,459 --> 00:15:03,540 on that solution so maybe in few years 329 00:15:01,620 --> 00:15:06,139 we'll have a blend of cloud computing 330 00:15:03,540 --> 00:15:08,579 and Edge Computing where we can get the 331 00:15:06,139 --> 00:15:11,459 scalability and reliability of cloud 332 00:15:08,579 --> 00:15:15,060 computing and the low latencies or 333 00:15:11,459 --> 00:15:17,639 security of edge computing 334 00:15:15,060 --> 00:15:20,760 so these are the takeaways from the from 335 00:15:17,639 --> 00:15:23,579 the talk cloud computing brings server 336 00:15:20,760 --> 00:15:26,519 closer closer to the data whereas in 337 00:15:23,579 --> 00:15:29,579 cloud computing we take the data closer 338 00:15:26,519 --> 00:15:31,380 to the server uh it's not a choice to 339 00:15:29,579 --> 00:15:32,760 choose but it's not our choice to choose 340 00:15:31,380 --> 00:15:35,100 between Edge Computing or cloud 341 00:15:32,760 --> 00:15:37,500 computing there could be a reliable 342 00:15:35,100 --> 00:15:40,320 solution which where we can get both the 343 00:15:37,500 --> 00:15:43,380 uh the benefits of both the Technologies 344 00:15:40,320 --> 00:15:45,660 and still Edge Computing is quite new 345 00:15:43,380 --> 00:15:47,459 and very few companies are working on it 346 00:15:45,660 --> 00:15:48,899 but maybe in the future we'll have 347 00:15:47,459 --> 00:15:51,839 something where we can have a mix of 348 00:15:48,899 --> 00:15:54,000 both the Technologies Edge Computing 349 00:15:51,839 --> 00:15:56,220 helps in reducing the latencies and 350 00:15:54,000 --> 00:15:58,560 optimize the real-time Solutions while 351 00:15:56,220 --> 00:16:01,260 in the case of cloud computing it is 352 00:15:58,560 --> 00:16:03,060 suitable for uh companies or 353 00:16:01,260 --> 00:16:05,760 organizations where the huge amount of 354 00:16:03,060 --> 00:16:08,459 data is is created and we need to 355 00:16:05,760 --> 00:16:10,620 centralize that manage that data every 356 00:16:08,459 --> 00:16:12,779 now and then so it's difficult for Edge 357 00:16:10,620 --> 00:16:15,120 Computing to manage that amount of data 358 00:16:12,779 --> 00:16:17,940 for that cloud computing is a still 359 00:16:15,120 --> 00:16:20,100 better choice hybrid solutions could be 360 00:16:17,940 --> 00:16:22,620 a next big thing in the industry where 361 00:16:20,100 --> 00:16:24,779 we can have the reliability of low 362 00:16:22,620 --> 00:16:25,320 latencies and have 363 00:16:24,779 --> 00:16:27,500 um 364 00:16:25,320 --> 00:16:29,940 scalability of cloud computing so 365 00:16:27,500 --> 00:16:32,459 companies like who are sell superbase 366 00:16:29,940 --> 00:16:35,639 are work working on it so maybe next few 367 00:16:32,459 --> 00:16:38,220 years we'll have a solution like that 368 00:16:35,639 --> 00:16:40,500 so thank you everyone you can connect 369 00:16:38,220 --> 00:16:42,240 with me on Twitter or LinkedIn and if 370 00:16:40,500 --> 00:16:43,860 you want to chat about cloud computing 371 00:16:42,240 --> 00:16:46,259 Edge Computing back-end Services 372 00:16:43,860 --> 00:16:48,230 developer advocacy I'll be happy to 373 00:16:46,259 --> 00:16:52,759 catch up thank you 374 00:16:48,230 --> 00:16:52,759 [Applause] 375 00:16:53,000 --> 00:16:57,120 now speaker is asked not to take 376 00:16:55,199 --> 00:16:59,279 questions at this time are you still 377 00:16:57,120 --> 00:17:00,779 okay yep 378 00:16:59,279 --> 00:17:02,160 um well thank you very much for the talk 379 00:17:00,779 --> 00:17:04,380 you've given me a lot to think about and 380 00:17:02,160 --> 00:17:06,059 here is a mug and a thank you card 381 00:17:04,380 --> 00:17:06,980 thank you very much and another round of 382 00:17:06,059 --> 00:17:12,670 applause for our speaker 383 00:17:06,980 --> 00:17:12,670 [Applause]