Would you like to inspect the original subtitles? These are the user uploaded subtitles that are being translated: 1 00:00:00,330 --> 00:00:07,340 If the next topic I want to discuss is Esseily now, you might have heard of Esseily before, since 2 00:00:07,350 --> 00:00:10,000 it's quite a common term in software architecture. 3 00:00:10,170 --> 00:00:12,780 But still, let's quickly reiterative. 4 00:00:13,290 --> 00:00:22,260 So SLA is a service level agreement and it basically defines the top 10 percent of a cloud service. 5 00:00:22,770 --> 00:00:25,380 Who is an example of some SLAC? 6 00:00:26,310 --> 00:00:35,370 So as you can see, a service which has 95 percent SLA actually means it can be done for 18 days, six 7 00:00:35,370 --> 00:00:38,970 hours, 17 minutes and 27 seconds annually. 8 00:00:40,110 --> 00:00:48,900 On the other end, a service with SLA of ninety nine point ninety nine percent can be done for 52 minutes 9 00:00:48,900 --> 00:00:50,920 and 35 seconds annually. 10 00:00:51,510 --> 00:00:59,070 So as you can see, there is a big difference between the various SLA is now when creating a new cloud 11 00:00:59,070 --> 00:01:05,240 service, always check the SLA of the service and let's look at some examples. 12 00:01:05,760 --> 00:01:14,190 So, for example, an up service in Azure can have ninety nine point ninety five percent SLA and sometimes 13 00:01:14,310 --> 00:01:19,200 it will have no SLA at all depending on the tier that is used. 14 00:01:21,010 --> 00:01:25,240 Another example is from Aju sequel, a database in. 15 00:01:26,170 --> 00:01:32,770 So as we can see, again, these results can have multiple isolator depends on the exact material that 16 00:01:32,770 --> 00:01:33,480 we are using. 17 00:01:33,850 --> 00:01:40,600 So when using the business critical or premium to configure asone redundant deployment, we have an 18 00:01:40,600 --> 00:01:48,370 SLA of ninety nine point nine nine five percent, which is great SLA and is actually the second best 19 00:01:48,640 --> 00:01:50,110 SLA in all. 20 00:01:50,200 --> 00:01:52,270 Ijaw not of course, right now. 21 00:01:52,270 --> 00:01:58,810 You have no idea what exactly is SQL database business critical or premium and what exactly is redundant 22 00:01:58,810 --> 00:01:59,380 deployment. 23 00:01:59,380 --> 00:02:00,880 And that's fine, we will discuss it. 24 00:02:01,330 --> 00:02:05,180 But it's still important that you see that SLA can differ. 25 00:02:05,470 --> 00:02:09,290 Depends on the exact tier and the pricing scheme we are using. 26 00:02:09,430 --> 00:02:15,070 So if you will take a look at the bottom line, you can see that sometimes amusical can have an easily 27 00:02:15,220 --> 00:02:18,480 as low as ninety nine point nine percent. 28 00:02:19,180 --> 00:02:26,080 Still, it's quite a high Esseily, but it pales in comparison to the ninety nine point nine nine five 29 00:02:26,080 --> 00:02:28,000 percent of the fixed line. 30 00:02:29,170 --> 00:02:35,740 Now, when talking about Italy, it's always important to remember that the actual leg of the system 31 00:02:35,980 --> 00:02:40,800 should be calculated and we can't just use the SLA of the resource we are using. 32 00:02:41,260 --> 00:02:48,970 So what it means is that in order to get the actual system ESSEILY, we need to multiply the value of 33 00:02:48,970 --> 00:02:50,350 the participating service. 34 00:02:50,770 --> 00:02:52,060 And let's see an example. 35 00:02:52,630 --> 00:02:54,640 Let's say we have an up service now. 36 00:02:54,640 --> 00:02:59,340 As we saw before, the service SLA is ninety nine point ninety five. 37 00:03:00,820 --> 00:03:08,380 And then we also have a equal database and it's SLA is ninety nine point ninety nine percent because 38 00:03:08,380 --> 00:03:15,040 that we are using in this case, has this Esseily now to get the actual SLA of the system, we need 39 00:03:15,040 --> 00:03:21,850 to multiply both the SLAC so we multiply ninety nine point ninety five and ninety nine point ninety 40 00:03:21,850 --> 00:03:26,470 nine and what we get is ninety nine point ninety four percent. 41 00:03:26,710 --> 00:03:27,850 And the this is our. 42 00:03:28,870 --> 00:03:34,750 No, this is only equal to five hours, 15 minutes and 34 seconds annual down time. 43 00:03:35,470 --> 00:03:40,360 Whether it's acceptable or not, that's naturally depends on the system requirements. 44 00:03:40,360 --> 00:03:46,270 But still, it's important to understand how exactly to calculate the actual SLA of the system. 4817