Original subtitles

1

If the next topic I want to discuss is Esseily now, you might have heard of Esseily before, since

2

it's quite a common term in software architecture.

3

But still, let's quickly reiterative.

4

So SLA is a service level agreement and it basically defines the top 10 percent of a cloud service.

5

Who is an example of some SLAC?

6

So as you can see, a service which has 95 percent SLA actually means it can be done for 18 days, six

7

hours, 17 minutes and 27 seconds annually.

8

On the other end, a service with SLA of ninety nine point ninety nine percent can be done for 52 minutes

9

and 35 seconds annually.

10

So as you can see, there is a big difference between the various SLA is now when creating a new cloud

11

service, always check the SLA of the service and let's look at some examples.

12

So, for example, an up service in Azure can have ninety nine point ninety five percent SLA and sometimes

13

it will have no SLA at all depending on the tier that is used.

14

Another example is from Aju sequel, a database in.

15

So as we can see, again, these results can have multiple isolator depends on the exact material that

16

we are using.

17

So when using the business critical or premium to configure asone redundant deployment, we have an

18

SLA of ninety nine point nine nine five percent, which is great SLA and is actually the second best

19

SLA in all.

20

Ijaw not of course, right now.

21

You have no idea what exactly is SQL database business critical or premium and what exactly is redundant

22

deployment.

23

And that's fine, we will discuss it.

24

But it's still important that you see that SLA can differ.

25

Depends on the exact tier and the pricing scheme we are using.

26

So if you will take a look at the bottom line, you can see that sometimes amusical can have an easily

27

as low as ninety nine point nine percent.

28

Still, it's quite a high Esseily, but it pales in comparison to the ninety nine point nine nine five

29

percent of the fixed line.

30

Now, when talking about Italy, it's always important to remember that the actual leg of the system

31

should be calculated and we can't just use the SLA of the resource we are using.

32

So what it means is that in order to get the actual system ESSEILY, we need to multiply the value of

33

the participating service.

34

And let's see an example.

35

Let's say we have an up service now.

36

As we saw before, the service SLA is ninety nine point ninety five.

37

And then we also have a equal database and it's SLA is ninety nine point ninety nine percent because

38

that we are using in this case, has this Esseily now to get the actual SLA of the system, we need

39

to multiply both the SLAC so we multiply ninety nine point ninety five and ninety nine point ninety

40

nine and what we get is ninety nine point ninety four percent.

41

And the this is our.

42

No, this is only equal to five hours, 15 minutes and 34 seconds annual down time.

43

Whether it's acceptable or not, that's naturally depends on the system requirements.

44

But still, it's important to understand how exactly to calculate the actual SLA of the system.